Skip to main content
Glama

Search Cluster Chronicles

search_chronicles
Read-onlyIdempotent

Search Cluster Chronicles works (writer-in-residence essays, poems, photos, events) by chronicler, form, year, subject, place or keyword. Text-only hits include snippets.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_chronicles"
  }
}

Input Schema

NameRequiredDescriptionDefault
formNoForm: essay, poem, still image, event, video
limitNoDefault 20, max 100
placeNoPlace at any level ('Kenya' includes Kakamega) or a venue, partial
offsetNo
personNoA chronicler, other credited person or person depicted; either name order works
keywordNoEvery word must occur in the title, abstract or text; quote a phrase to match it exactly
subjectNoSubject, partial
year_toNoLatest year
languageNoName or ISO code
year_fromNoEarliest year

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, non-destructive, idempotent, closed-world search. The description adds useful behavioral context that text-only hits include snippets, but it does not elaborate on result structure, pagination behavior, or limitations beyond that single note.

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?

The description is two compact sentences with no wasted wording, and the primary purpose is front-loaded. The parenthetical examples are useful and do not distract from the core search behavior.

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 10-parameter search tool with no required parameters, 90% schema coverage, and strong annotations, the description provides enough context to understand the tool's scope and main search facets. It could be slightly more complete regarding result behavior beyond snippets, but the schema and annotations cover most operational details.

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 90%, so the input schema already carries most parameter meaning. The description maps several schema parameters to natural search dimensions, but it does not add syntax, edge-case, or selection guidance beyond what the schema provides, making the baseline score appropriate.

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 uses a specific verb, "Search," and a clearly scoped resource, "Cluster Chronicles works," and lists the content types being searched. It is clear what the tool does, though it does not explicitly distinguish itself from sibling search tools such as search_persons or search_videos.

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

Usage Guidelines3/5

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

The description implies when the tool is useful by naming the dimensions it searches, such as chronicler, form, year, subject, place, or keyword. It does not explicitly say when to use this instead of sibling search tools or when not to use it, so the guidance is adequate but inferred.

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.