Skip to main content
Glama

TraceVero

Search tracevero

search
Read-onlyIdempotent

Find public MCP servers or coding agents by name, task, package coordinate or URL, using the same staged search as the website. Returns IDs for fetch.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
limitNo
queryYesName, task, package coordinate or URL. Provider text is searched literally before broader fallback stages.
localeNoen
offsetNo

Output Schema

NameRequiredDescriptionDefault
totalYes
offsetYes
resultsYes
web_urlYes
has_moreYes
returnedYes
next_offsetYes
search_stageYes
dataset_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds that matching is 'staged' like the website, which hints at literal-first fallback behavior, but it does not explain ranking, whether loose matches appear, or how pagination interacts with results beyond what the schema says.

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

Conciseness4/5

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

Two sentences, front-loaded with what is searched and how results are used. The phrase 'using the same staged search as the website' is a little imprecise, but nothing is redundant.

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

Completeness3/5

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

An output schema exists, so the return format need not be described. However, for a tool with five parameters, two enums, and low schema coverage, leaving type/locale/limit/offset semantics entirely undocumented makes the definition only minimally sufficient.

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

Parameters2/5

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

Schema description coverage is only 20%: only 'query' is documented in the schema, and the description merely restates its facets. The 'type' enum, 'locale', 'limit' (max 20) and 'offset' (max 100000) get no explanation in either place, so the description does not compensate for the coverage gap.

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 (Find) plus the exact resource (public MCP servers or coding agents) and the matchable facets (name, task, package coordinate, URL). 'Returns IDs for fetch' also ties it to the companion tool, so the agent can distinguish search from fetch without opening either 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?

Makes the workflow intent clear: search produces IDs, then fetch retrieves details. It does not name any exclusion or say when a sibling such as compare or get_connection_options is preferable, so it stops short of full when/when-not guidance.

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