Skip to main content
Glama

Prior Ledger

get_thread

Read-only

Every entry on one subject, oldest first, with each entry's status: use it to see how a question was settled over time.

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": {
      "subject": "<subject>"
    },
    "name": "get_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
subjectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description usefully adds that results are ordered oldest-first and that each entry carries a status field. It omits volume/pagination behavior and the failure mode for a nonexistent subject, which matters for a thread that could be long.

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?

One tight sentence with the content and ordering front-loaded, then the use case. No restatement of the name, no filler.

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 single-parameter, read-only, non-open-world tool with no output schema, the definition covers what is returned and in what order. Only edge behavior — pagination or unknown subject — is left unspecified.

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 0%, so the definition carries the burden for the single `subject` parameter. It says entries are "on one subject," implying subject is the scoping key, but adds nothing about matching semantics (exact string vs fuzzy), case sensitivity, or what happens for an unknown subject.

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 retrieval: every entry on one subject, ordered oldest first, each with its status. That is concrete enough for an agent to pick it over get_entry (single entry) without opening either schema. It stops short of naming the sibling it differs from.

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?

"use it to see how a question was settled over time" gives a real usage condition — historical/chronological view of one subject. But it gives no exclusions: nothing tells the agent when to prefer get_entry or search_precedent instead, leaving the choice to inference from names.

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.