Skip to main content
Glama

Search Cassie Hour public records

search_public_story_records
Read-onlyIdempotent

Search the integrity-mapped public What Happened catalog by topic, ID or title. Returns matching summaries, canonical links, source IDs and review-copy references/hashes; private archives are not searched. No authentication required. Call get_public_story_record with a returned story_id to read one mapped packet; no match is not proof that no private record exists.

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

Input Schema

NameRequiredDescriptionDefault
queryYesRequired public-record search text, 2–240 characters; IDs, titles and subject terms are accepted.
max_resultsNoOptional match limit from 1 to 10; defaults to 5.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / max_results / description
      Added value: +"Optional match limit from 1 to 10; defaults to 5."
    • addedInput schema / properties / query / description
      Added value: +"Required public-record search text, 2–240 characters; IDs, titles and subject terms are accepted."
  2. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (read-only, idempotent, open-world, non-destructive), the description adds genuinely new behavioral facts: no authentication is required, private archives are explicitly out of scope, the shape of the returned matches, and the epistemic caveat about null results. With no output schema, this return-content disclosure carries real weight.

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?

Three dense sentences with the core action front-loaded and no filler. The 'review-copy references/hashes' phrase is slightly jargon-heavy but still earns its place as return-value information.

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?

For a two-parameter search with full schema coverage and no output schema, the description covers scope, auth, return content and the null-result caveat, so an agent can call it correctly. The one gap is that it does not tell the agent how to choose between this and search_cassie_hour_fragments.

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 description's 'by topic, ID or title' largely restates what the query parameter already documents ('IDs, titles and subject terms are accepted'). No added syntax, ranking or matching semantics, so the baseline 3 applies.

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?

The description names a specific verb and resource — searching the 'integrity-mapped public What Happened catalog' — and lists the accepted match facets (topic, ID, title). It is clearly distinct from the read-one sibling it routes to, get_public_story_record, though it never contrasts itself with the other search sibling, search_cassie_hour_fragments.

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?

It gives clear follow-up guidance (call get_public_story_record with a returned story_id to read one mapped packet) and an important boundary condition ('no match is not proof that no private record exists'). What it lacks is an explicit when-to-use-this-instead-of statement versus the other search tool in the family.

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