Skip to main content
Glama

Search the index (ChatGPT-compatible)

search
Read-onlyIdempotent

For ChatGPT connectors and deep research only; other clients use search_vendors. Free-text search in the id-only shape they require: returns ids, titles and URLs of vendors, price summaries and cost pages, to open with fetch. Words for a service, an area, an event type and a dollar amount narrow the results. Other clients get full results in one call from search_vendors (structured filters, vendor cards) or get_price_summary (what a service costs).

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
queryYesWhat to look for in plain words, e.g. "wedding DJ Brooklyn under 2000" or "how much does a florist cost in Queens".

Output Schema

NameRequiredDescriptionDefault
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/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 still adds real behavior: the id-only result shape and the follow-up workflow ("to open with fetch"), which an agent could not infer from annotations alone.

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

Conciseness3/5

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

The routing information is front-loaded, but the text is repetitive: search_vendors is named twice and "other clients" appears twice in a four-sentence block. The parenthetical "(structured filters, vendor cards)" is useful, yet the whole passage could lose a sentence without losing meaning.

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?

A single-parameter read tool with an output schema and full annotations needs little more; routing, query semantics and the fetch hand-off are all covered. Only the slight redundancy keeps it from being fully tight.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description goes beyond it by explaining that words for a service, area, event type and dollar amount are what actually narrow results. That is genuine guidance the schema's example alone does not spell out.

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?

The description names a specific verb+resource ("Free-text search in the id-only shape") and explicitly separates it from search_vendors and get_price_summary. An agent can tell which tool this is and what it returns (ids, titles, URLs of vendors) without opening the schema.

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

Usage Guidelines5/5

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

Explicit when-to-use ("For ChatGPT connectors and deep research only") and when-not ("other clients use search_vendors"), with two named alternatives and the condition that selects each. Nothing is left to inference.

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