Skip to main content
Glama

Get Cluster Chronicles work

get_chronicle
Read-onlyIdempotent

One Cluster Chronicles work: chroniclers and roles, people depicted, subjects, places, related works and recordings, images, links. Abstracts are AI-written (says which model). Text opt-in and pageable.

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": {
      "id": "<id>"
    },
    "name": "get_chronicle"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesId from search_chronicles, e.g. 50109, or chronicle:50109
text_offsetNoStart offset into the text (chars), with include_text
include_textNoDefault false — set true to include the full text of an essay or poem
text_max_charsNoMax text characters to return (default/max 25000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add provenance and behavior detail. It does: abstracts are AI-written and disclose which model, full text is opt-in (default off) and pageable — meaningful context an agent would not get from the annotations alone. It stops short of describing response shape or size limits beyond what the schema carries.

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?

A single dense sentence with the resource front-loaded and no filler; every clause names concrete content or behavior (AI-written abstracts, opt-in pageable text). Nothing is padding, though the fragment style means the reader must supply the verb.

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?

With no output schema, the description carries the burden of saying what comes back, and it does by enumerating the record's sections, plus it explains text pagination and the AI provenance of abstracts. What remains thin is the id resolution nuance (numeric vs 'chronicle:' prefix) and guidance on choosing this over siblings.

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 all four parameters are already documented with defaults, bounds, and id formats, making 3 the baseline. 'Text opt-in and pageable' restates include_text and the offset/max-chars pair without adding syntax or behavior beyond the schema, so no credit above baseline.

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 identifies a specific resource (a single Cluster Chronicles work) and enumerates what it contains: chroniclers and roles, people depicted, subjects, places, related works and recordings, images, links. The retrieval verb is elided into a noun phrase, and no sibling tool is named for contrast, but an agent can still tell this is a single-record fetch rather than the search tool (the id parameter in the schema says 'Id from search_chronicles').

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?

Usage context is only implied: this is the per-record companion to the search tool, keyed by an id. 'Text opt-in and pageable' hints at when the optional parameters matter, but there is no explicit statement of when to prefer this over search_chronicles or resolve_entity, and no stated prerequisites.

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.