Skip to main content
Glama

Search facts

search_facts
Read-onlyIdempotent

Keyword search over sourced facts: each hit is a claim with the speaker's exact quote, timestamp, episode and links. Best for 'what did X say about Y' (search 'X Y', not the whole question). Results include show_slug and episode_slug for get_episode or get_transcript. Pages via offset/next_offset; total counts all matches; match says how strictly the keywords matched.

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

Input Schema

NameRequiredDescriptionDefault
showNoOnly search this show: slug or title from list_shows
limitNoHow many to return, 1-20, default 10
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.
offsetNoHow many to skip, default 0. Pass next_offset from the previous page to get the next page.

Output Schema

NameRequiredDescriptionDefault
hintNo
noteNo
matchNo
totalYes
offsetYes
resultsYes
next_offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world behavior, so the description's value is in operational details it does supply: offset/next_offset paging, that total counts all matches, and that match reports match strictness. Ordering behavior (all-keyword hits first, then partial) is disclosed in the schema rather than the description, so this is not fully complete.

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?

A single dense paragraph, front-loaded with the resource and the primary use case, with no filler sentences. Some clauses (results include show_slug/episode_slug, total and match semantics) partially restate structured output information, which is mild redundancy but informative.

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?

Given an output schema already exists, the description need not explain return values, yet it still flags the key fields an agent must act on (slugs for follow-up calls, next_offset for paging). Combined with query-formulation guidance, an agent has everything needed to call it correctly.

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. The description goes beyond the schema by advising the query be 2-4 distinctive words rather than a full question, and by explaining the offset/next_offset continuation loop — practical meaning the schema's field descriptions do not fully convey.

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

Purpose4/5

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

States a specific verb and resource (keyword search over sourced facts) and defines what a hit is — a claim with quote, timestamp, episode and links. It also clarifies the search is literal keyword, not semantic. It does not explicitly distinguish itself from the sibling search_transcripts, so sibling differentiation is only implicit.

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 concrete use case ('what did X say about Y') and query-shaping advice ('search X Y, not the whole question'), which is real when-to-use guidance. It stops short of naming an alternative tool or stating when not to use it.

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