Ranked full-text search across the SvGrid documentation and demo catalogue. Returns the best pages first with an excerpt and an id you pass to fetch. Use this before writing SvGrid code so the API names come from the docs rather than from memory.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results, default 10, max 25. | |
| query | Yes | What you are looking for, e.g. "row virtualization". |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral disclosure burden. It states the search is ranked, returns results ordered by relevance, includes an excerpt and an id, and positions the tool as a docs lookup. It stops short of describing edge cases like empty results or formatting, but for a search tool this is solid context.
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?
Two sentences with no filler. The first sentence states what the tool does and what it returns; the second gives direct usage guidance. Everything earns its place.
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?
For a two-parameter search tool with full schema coverage, the description is nearly complete. It even explains how the output connects to the fetch sibling. A more explicit output shape or mention of limit behavior would help, but nothing essential is missing for correct 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 coverage is 100%: both query and limit are described with types, defaults, and an example. The description adds no parameter-level meaning beyond that, so the schema already does the heavy lifting and the baseline 3 applies.
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 names a specific verb and resource: 'Ranked full-text search across the SvGrid documentation and demo catalogue.' It also clarifies what the tool returns (best pages, excerpt, id for fetch), which distinguishes it from siblings like fetch and get_api_reference.
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 gives clear timing guidance: 'Use this before writing SvGrid code so the API names come from the docs rather than from memory.' It does not explicitly contrast with alternatives like get_api_reference or list_examples, but the use-before-coding context is strong.
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.
The search→fetch and list_examples→get_example_source pairs form clear workflows, and check_svgrid_code is distinct. The only real ambiguity is that fetch also accepts a demo id, which overlaps somewhat with get_example_source, though fetch returns page text rather than .svelte source.
Most tools follow a descriptive verb_noun pattern: get_api_reference, get_example_source, list_examples, check_svgrid_code. The bare verbs search and fetch are minor deviations, but the names remain predictable and easy to distinguish.
Six tools is a tight, well-scoped set for a documentation-and-code-support server. Each tool earns its place and together they cover discover, read, reference, example, and verify workflows without redundancy.
The tool surface covers the full assistant loop: search documentation, fetch doc content, read the API reference, browse and copy demo source, and validate code against the real SvGrid API. There is no obvious missing operation that would create a dead end for an agent.