Skip to content

Small improvements - #201

Open
Rifdhan wants to merge 1 commit into
mainfrom
tool-description-tweaks-small-improvements
Open

Small improvements#201
Rifdhan wants to merge 1 commit into
mainfrom
tool-description-tweaks-small-improvements

Conversation

@Rifdhan

@Rifdhan Rifdhan commented Aug 13, 2026

Copy link
Copy Markdown
Collaborator
  • Update iframe_url description to mention stripping tsmcp flag if presenting links to the user
  • Improve error logging with more details
  • Add additional Honeycomb metrics tracking

- Update iframe_url description to mention stripping tsmcp flag
  if presenting links to the user
- Improve error logging with more details
- Add additional Honeycomb metrics tracking
@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Updated (UTC)
✅ Deployment successful!
View logs
rifdhan-test-app 26be378 Aug 13 2026, 11:33 PM

{
...GET_SESSION_UPDATES_SHARED_TOOL_DEFINITION,
description: GET_SESSION_UPDATES_RAW_DESCRIPTION,
description: `${GET_SESSION_UPDATES_SHARED_TOOL_DEFINITION.description} The \`session_updates\` are returned in their raw and unmodified form. The shape of each update may be different, and there are no guarantees on what fields may be present. For \`answer\` updates, the \`answer_id\` field will not be present (for use with the \`create_liveboard\` tool). You can reconstruct this field using the following formula: \`answer_id = JSON.stringify({ session_id: answer_update.metadata.session_id, gen_no: answer_update.metadata.gen_no })\`.`,

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

create_dashboard instead of create_liveboard

Comment thread src/servers/mcp-server.ts
const span = trace.getSpan(context.active());
span?.setAttribute(
"enable_raw_session_updates",
this.ctx.props.enableRawSessionUpdates ?? "(not passed)",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

String(this.ctx.props.enableRawSessionUpdates ?? "(not passed)").

Comment thread src/servers/mcp-server.ts
const span = this.initSpanWithCommonAttributes();
span?.setAttribute(
"enable_raw_session_updates",
this.ctx.props.enableRawSessionUpdates ?? "(not passed)",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

String(this.ctx.props.enableRawSessionUpdates ?? "(not passed)")

Comment thread src/streaming-utils.ts
"Error event in event stream, error code",
item.error_code,
);
console.error("Error event in event stream:", item);

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

event item might be big json. Not sure if we should log the whoe thing.

{
...GET_SESSION_UPDATES_SHARED_TOOL_DEFINITION,
description: GET_SESSION_UPDATES_RAW_DESCRIPTION,
description: `${GET_SESSION_UPDATES_SHARED_TOOL_DEFINITION.description} The \`session_updates\` are returned in their raw and unmodified form. The shape of each update may be different, and there are no guarantees on what fields may be present. For \`answer\` updates, the \`answer_id\` field will not be present (for use with the \`create_liveboard\` tool). You can reconstruct this field using the following formula: \`answer_id = JSON.stringify({ session_id: answer_update.metadata.session_id, gen_no: answer_update.metadata.gen_no })\`.`,

@mouryab mouryab Aug 14, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For answer updates, shouldn't we have answer_id

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants