Skip to main content
Glama

Search (connector form)

search
Read-onlyIdempotent

Search the registry; returns results with id, title and url. A thin wrapper over search_mechanisms for connectors that expect a search and a fetch tool. It looks in all review states and marks entries in review in the title. Entries describe processes in general, not the present state of any country, market or asset.

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
queryYesSearch query. Not empty.

Output Schema

NameRequiredDescriptionDefault
noteNo
scopeNoScope of the registry: what the entries are and are not.
resultsYes
attributionNoCC BY 4.0 attribution: how an answer that uses the entries names the source.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 genuine context beyond that: results span all review states and in-review entries are flagged in the title, and the content is general process material rather than live state. It does not discuss result limits, ordering, or pagination, which leaves some behavioral gaps for a search endpoint.

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?

Front-loads the purpose and return fields, then qualifies the wrapper relationship and the content caveat. Every sentence carries information; the phrasing is slightly dense but no clause is wasted.

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

Completeness5/5

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

For a one-parameter read tool with an output schema and full annotations, the description covers everything an agent needs: what is searched, what comes back, why this wrapper exists versus the sibling, and how to interpret review-state markers and content scope.

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?

There is a single parameter with 100% schema description coverage, so the schema already documents it including the non-empty constraint. The description adds no query syntax, matching behavior, or formatting guidance beyond what the schema supplies, which is the expected baseline.

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 ('Search the registry'), names the returned fields (id, title, url), and explicitly differentiates itself from the sibling search_mechanisms by framing itself as a thin wrapper. An agent can identify what it does and how it differs from siblings 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?

Gives a clear selection condition: use this one when the connector expects a search-and-fetch pair, otherwise search_mechanisms is the underlying tool. It also warns that entries describe processes in general rather than present country/market/asset state, which shapes when results are appropriate. It stops short of explicit when-not-to-use or prerequisites, so it is strong but not exhaustive.

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.