Skip to main content
Glama

Search (ChatGPT-style)

search
Read-onlyIdempotent

Search facts, transcript passages and topics at once, for clients that only use the generic search/fetch pair (ChatGPT Deep Research). Returns up to 10 ids with a title, link and short snippet; pass an id to fetch for the full text. Other clients should prefer search_facts (quotes with speaker and timestamp) or search_transcripts (raw passages), which page and filter by show.

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
queryYesKeywords, matched literally (stemmed full-text search, not semantic). Best with 2-4 distinctive words such as names, companies or terms, e.g. "Jensen Huang data centers". Filler and question words are ignored; results matching every keyword come first, then results matching some of them.

Output Schema

NameRequiredDescriptionDefault
hintNo
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/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, and an output schema exists, so the baseline burden is low. The description still adds non-redundant behavior: a hard cap of 10 results, the fields returned per hit (title, link, short snippet), and the id→fetch chaining workflow. It does not discuss pagination or ranking caveats beyond what the query parameter already states.

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?

Two sentences with zero waste. The primary use case is front-loaded, then the return shape and fetch handoff, then the routing caveat — a sensible order with no repetition of the schema.

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-only search tool with annotations and an output schema, everything an agent needs is present: eligibility, result cap, per-hit fields, the fetch follow-up, and where to go instead when filtering or paging is required.

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% and the single `query` parameter is documented in detail there (literal stemming, 2-4 distinctive words, filler ignored, all-keyword-first ranking). The description adds nothing about the parameter itself; its extra detail concerns result counts and fetch chaining instead. Baseline 3 is appropriate when the schema fully carries parameter meaning.

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 facts, transcript passages and topics at once") and immediately scopes it to a client class ("clients that only use the generic search/fetch pair"). It names the siblings it is not (search_facts, search_transcripts) and characterizes them, so an agent can distinguish it without opening another 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?

Gives explicit when-to-use (generic search/fetch-only clients), explicit when-not ("Other clients should prefer..."), and names both alternatives along with their differentiators (quotes with speaker/timestamp vs raw passages, plus paging and show filtering). This is full routing guidance rather than an implied context.

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