Skip to main content
Glama

Get source citations

mcai_cite
Read-onlyIdempotent

Returns recorded source citations for a term, including document, section, exact quotation, character range and edition, so callers can audit, quote or display sources without fetching the full entry.

Instructions

Return only the source citations for a term: document, section, exact quotation, character range and edition. Use when the caller needs to audit, quote or display sources without the full entry. Routing: full entry -> mcai_concept; provenance chain across documents and editions -> mcai_provenance; definitions with citations -> mcai_answer. Boundary: returns recorded sources only; never invents a citation.

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": {
      "term": "<term>"
    },
    "name": "mcai_cite"
  }
}

Input Schema

NameRequiredDescriptionDefault
termYesExact term name, alias, or slug.
limitNoMaximum number of citations to return (default 5).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.8

TDQS

A4.5/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, closed-world, non-destructive), so the bar is lower. The description still adds real value with the boundary statement 'returns recorded sources only; never invents a citation' and by naming the exact shape of returned records. It stops short of describing truncation or what happens when a term matches multiple editions beyond referencing the limit.

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 purpose is front-loaded, and the remainder is partitioned into labeled 'Routing:' and 'Boundary:' clauses. No sentence is redundant, and the field list is packed inline rather than padded into prose.

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?

There is no output schema, so the description carries the return-value burden and does so by enumerating the citation fields. With only two parameters and full schema coverage, everything an agent needs to select and invoke this tool is present.

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 'term' and 'limit' are fully documented in the schema. The description adds no syntax, matching behavior, or alias-resolution detail beyond what the schema already provides, so the baseline of 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?

The description opens with a specific verb and resource ('Return only the source citations for a term') and enumerates the returned fields (document, section, exact quotation, character range, edition). It also separates itself from siblings by contrasting with the full entry returned by mcai_concept.

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?

It states an explicit use case ('when the caller needs to audit, quote or display sources without the full entry') and provides a routing block mapping three alternatives — mcai_concept, mcai_provenance, mcai_answer — to their distinguishing conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.