Skip to main content
Glama

Get approved citations for source keys

get_rule_citations
Read-onlyIdempotent

Returns passage-level citations only when the linked rule satisfies the two-reviewer publication gate and has no blocking review. Unresolved keys are returned separately; draftSources names the book line (no text) behind any unresolved key the code cites, marked not reviewed.

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": {
      "sourceKeys": "<sourceKeys>"
    },
    "name": "get_rule_citations"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceKeysYes

Output Schema

NameRequiredDescriptionDefault
citationsYes
draftSourcesYes
publicationRuleYes
unresolvedSourceKeysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / draftSources
      Added value: +{
      +  "type": "array"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "citations",
      -  "unresolvedSourceKeys",
      -  "publicationRule"
      -]New value: +[
      +  "citations",
      +  "unresolvedSourceKeys",
      +  "draftSources",
      +  "publicationRule"
      +]
  2. Added

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the description is not burdened with safety disclosure. It adds genuinely non-obvious behavioral context: the two-reviewer publication gate, the no-blocking-review condition, and that unresolved keys are returned separately rather than failing the call. What it omits is any statement about partial results or limits on how many keys can be unresolved before failure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences with the gating rule front-loaded ahead of the unresolved-key edge case, which is the right ordering. The second sentence is jargon-heavy ('draftSources names the book line (no text)') but every clause carries information.

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 an output schema present, the description needn't enumerate return fields, and annotations cover the safety profile. What remains is nearly complete for a read-only lookup; the sole meaningful gap is the undefined notion of a source key, which matters because it is the only input.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required parameter, so the description must carry the load, and it does not: it never explains what a 'source key' is, its format, or that up to 50 may be supplied. The phrase 'unresolved keys' hints that keys can fail to resolve, but the agent is left guessing at the input vocabulary.

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 (Returns) with a precisely scoped resource: passage-level citations gated on rule publication status. It implies a distinction from siblings like search_source_passages or get_book_rule_findings by emphasizing 'approved' and 'two-reviewer publication gate', but it never names an alternative outright, so the differentiation is inferential rather than explicit.

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 gating condition ('only when the linked rule satisfies the two-reviewer publication gate and has no blocking review') implies this is the tool to call for vetted citations, but the description gives no explicit when-to-use guidance or comparison to sibling citation/rule lookup tools. The agent must infer that this is the approval-filtered counterpart to raw passage search.

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