Skip to main content
Glama

Search Cassie Hour fragments

search_cassie_hour_fragments
Read-onlyIdempotent

Search the public fragment/essay index by topic and return ranked matching fragment IDs, summaries and links. Use this for essay discovery, not the mapped event-record catalog (search_public_story_records) or one record's full text (get_public_story_record). No authentication required; zero matches means no indexed match.

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

Input Schema

NameRequiredDescriptionDefault
queryYesRequired public-fragment search text, 1–1000 characters; use topic/interest words, not a guessed fragment ID.
max_resultsNoOptional result count 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 result count from 1 to 10; defaults to 5."
    • addedInput schema / properties / query / description
      Added value: +"Required public-fragment search text, 1–1000 characters; use topic/interest words, not a guessed fragment ID."
  2. 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, openWorld and non-destructive behavior, so the safety profile is covered. The description adds two genuinely useful facts beyond that: no authentication is required, and zero matches means no indexed match (result semantics for the empty case), though it doesn't explain ranking behavior.

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?

Three tight sentences with zero redundancy; the core scope statement is front-loaded, followed by sibling disambiguation and operational notes.

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?

With no output schema, the description usefully names the return payload (ranked fragment IDs, summaries, links), plus auth requirements and empty-result semantics and sibling alternatives — everything needed to call this tool correctly.

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%, so both parameters and their bounds (1–1000 chars, 1–10 results, default 5) are already fully documented. The description implies topic-based querying but adds no syntax or formatting detail beyond the schema, so baseline 3 applies.

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 public fragment/essay index by topic — and explicitly names the two siblings it is not (search_public_story_records and get_public_story_record). An agent can route correctly without opening any 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?

Explicitly says to use it for essay discovery rather than the mapped event-record catalog or one record's full text, and names both alternatives. When-to-use and when-not-to-use are both present.

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