Skip to main content
Glama

Caelara Labs Agent Safety

citation_extractor

Extract URLs, DOIs, arXiv ids and author-year citations

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": {
      "text": "<text>"
    },
    "name": "citation_extractor"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText containing citations

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and it discloses almost nothing: not the output shape, not whether duplicates are merged, not whether DOIs/arXiv ids are validated or normalized, not whether results are deduplicated or de-duplicated across citation styles. The only behavioral hint is the implicit read-only, non-destructive nature of 'Extract'. For a tool with zero annotation coverage this is a substantial gap.

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 front-loaded sentence with zero padding; every word names a distinct extraction target. Nothing could be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description is the only source of information about what comes back, and it never states the return structure (per-citation objects? a flat list? counts?). For an extraction tool whose entire value lies in its output, this leaves the agent guessing about how to consume results.

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 coverage is 100% and the single 'text' parameter is already documented as 'Text containing citations', so the description adds essentially nothing beyond the schema. It does not clarify size limits, encoding expectations, or whether multiple documents can be concatenated. Baseline 3 is appropriate where the schema does the work.

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?

Specific verb ('Extract') plus the exact resource categories it pulls out: URLs, DOIs, arXiv ids, author-year citations. An agent can immediately tell this is a text-in/citations-out extraction tool. No sibling differentiation is offered, but none is needed since the listed siblings do unrelated validation/compression work.

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

Usage Guidelines2/5

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

There is no statement of when to reach for this tool, when not to, or what to do if the text turns out to contain no citations. Usage is only inferable from the verb and the field list. The description also does not say whether it works on arbitrary prose, reference lists, or both.

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