Add tool descriptions so Amazon Q / kiro-cli load all tools#1
Open
igorsf wants to merge 1 commit into
Open
Conversation
Every tool except `index-notes` was registered via the 3-arg `server.tool(name, schema, handler)` overload, which emits no `description` field in `tools/list`. Amazon Q CLI / kiro-cli (and likely other clients that route MCP tools through Bedrock's Converse toolConfig API) silently drop description-less tools at load time — no error, they just never reach the model. (Bedrock's ToolSpecification.description is technically optional, but min-length 1 when present, and these clients choose to filter tools that omit it.) Net effect on those clients: 22 of 23 tools vanish. Only `index-notes` survived (it has a description via registerAppTool), so the model could ONLY start the fire-and-forget background indexer — and never poll it, since `index-notes-status` was also dropped. Indexing appeared to "start and never finish." search-notes, find-notes, get-note, index-notes-blocking, etc. were all invisible. Switch all 22 affected registrations to the 4-arg `server.tool(name, description, schema, handler)` overload. Descriptions only — no schema, handler, or behavior changes; strictly additive metadata that spec-compliant clients already tolerated. Verified by wire-tapping a kiro-cli session: tools/list now exposes 23/23 tools with descriptions (was 1/23 reaching the model), and the model can call search-notes and index-notes-blocking successfully.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
All tools except
index-noteswere registered without adescription.On Amazon Q CLI / kiro-cli this silently drops 22 of the 23 tools before
they ever reach the model. This PR adds a one-line description to every
tool registration.
The bug
Bare
server.tool(name, schema, handler)produces atools/listentrywith no
descriptionfield. Amazon Q CLI / kiro-cli — and likelyother clients that route MCP tools through Bedrock's Converse
toolConfigAPI — filter out tools that lack a description, withouterroring. (Bedrock's
ToolSpecification.descriptionis technicallyoptional, but has a min length of 1 when present; these clients choose
to drop tools that omit it.)
Result: only
index-notes(the lone tool with a description, viaregisterAppTool) was exposed. The model could start the backgroundindexer but had no
index-notes-status,index-notes-blocking,search-notes,find-notes,get-note, etc. So indexing "started andnever completed," and nothing was searchable.
A spec-compliant MCP client (the reference Inspector, a raw stdio probe)
keeps description-less tools, which is why this doesn't reproduce
everywhere.
Fix
Switch all 22 affected
server.tool(...)calls to the 4-arg overloadserver.tool(name, description, schema, handler). Descriptions only; nologic, schema, or handler changes.
Verification
Wire-tapped the JSON-RPC stream between kiro-cli and the server:
tools/listdescriptionAfter the change the model calls previously-invisible tools —
index-notes-blockingreturnsIndexed N chunks…in one step, andsearch-notesreturns results.bun buildclean.Scope / risk
Additive metadata only. No effect on spec-compliant clients (they
already loaded every tool); fixes Amazon Q / kiro-cli and similar.