Skip to main content
Glama

Velvet Developer Docs

Search the Velvet docs

search_docs
Read-only

Full-text search over the Velvet developer docs (Toy SDK and Velvet Live). Returns the best-matching sections as Markdown, each with its source URL. Use get_doc for a whole page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many sections to return
queryYesWhat to look for, e.g. "vibrate durationMs" or "mint model token"
productNotoys = Toy SDK, live = Velvet Live (cam sites)all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds genuinely new behavior: results are best-matching sections rendered as Markdown, each with a source URL. It adds nothing about ranking, empty-result behavior, or result-size limits, keeping it out of the top band.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with what is searched and what comes back, then the sibling routing. No filler, no restatement of the title, and every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description correctly compensates by stating the return shape (Markdown sections plus source URL) and the scope of the corpus. Missing only minor call-relevant detail such as how results rank or what an empty result set looks like.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so query, limit, and product are all documented with examples and an enum explanation in the schema itself. The description's word 'sections' loosely aligns with the limit parameter but adds no syntax, formatting, or query-shaping guidance beyond the structured fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Full-text search over the Velvet developer docs') and scopes it to the two doc families (Toy SDK and Velvet Live). Combined with the explicit contrast to get_doc, an agent can distinguish it from siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names an alternative and the condition that selects it ('Use get_doc for a whole page'), which is real routing guidance rather than an implied hint. It does not address the other siblings (get_recipes, get_toy_kinds) or when this search is the wrong tool for non-doc lookups, so it falls just short of fully explicit when/when-not coverage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources