Search the parsed spec by clause id / aoid / title (+ step text with search_steps). Aoid-exact ranks first. at: '<sha>' searches a historical main snapshot.
| Name | Required | Description | Default |
|---|---|---|---|
| at | No | ||
| spec | No | ||
| limit | No | ||
| query | Yes | ||
| edition | No | ||
| search_steps | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It discloses ranking behavior (aoid-exact first) and the `at` parameter for historical search. However, it does not explicitly state that the tool is read-only or describe response format, pagination, or error handling, leaving some behavioral aspects unclear.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise, using three short sentences to convey search modes, ranking, and historical search. No unnecessary information is included, and all sentences add value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity (6 params, no output schema, many siblings), the description covers core functionality and key behavioral details but omits parameter details and output format. It is adequate for a search tool but leaves gaps that could affect proper invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must explain parameters. It explains `search_steps` and `at` partially, but fails to explain `spec`, `limit`, `edition`, and how multiple search criteria interact. The `query` parameter is implied but not formally described, leaving ambiguity for agent use.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly specifies the tool's purpose: searching the parsed spec by clause ID, aoid, or title, with step text search via `search_steps`. It distinguishes itself from sibling tools like clause.get (retrieval) and spec.global_search (broader search) by detailing specific search modes and ranking behavior.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides context on when to use the tool (for searching by various identifiers and historical snapshots) but does not explicitly state when to avoid it or offer comparisons to siblings. The `search_steps` parameter hints at a use case, but no alternatives or exclusions are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct function: clause operations vs. proposal queries vs. spec utilities vs. test262 search. Even the two search tools have clear differences (single vs. cross-spec).
All tools follow a consistent `domain.action` pattern using lowercase and snake_case for the action (e.g., `clause.get`, `spec.global_search`, `test262.search`). No mixing of conventions.
17 tools is appropriate for a comprehensive TC39 spec browser. Each tool serves a specific need without redundancy, covering clauses, proposals, grammar, symbols, tables, and test262.
The toolset covers the full lifecycle of exploring TC39 specifications: retrieving clauses, searching, cross-referencing, diffing editions, inspecting grammar and symbols, and querying proposals and test262.