Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_agent_citation_extractor

Extracts URLs, DOIs, arXiv IDs, and author-year citations from text to help agents verify sources and avoid unsupported claims.

Instructions

[Agent Safety] Extract URLs, DOIs, arXiv ids and author-year citations Measured p50 11 ms, p95 15 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://agent.caelaralabs.com.

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": "caelara_agent_citation_extractor"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText containing citations

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does usefully disclose p50/p95 latency and that the tool calls an external host (https://agent.caelaralabs.com), which signals a remote network dependency, but it never says what the call returns, whether the input text is transmitted off-site, or how failures surface.

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 short sentences with the core capability front-loaded and no padding. The benchmark clause with a future-dated measurement and URL is somewhat noisy, and the missing punctuation between "citations" and "Measured" slightly hurts readability.

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 one-parameter extraction tool this is close to adequate: capability, latency profile, and remote endpoint are all stated. The notable gap is the absence of an output schema combined with no textual description of the return shape (flat list? typed groups?), which an agent would want before parsing 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?

There is a single required parameter at 100% schema description coverage ("Text containing citations"), so the schema already conveys its meaning. The description adds no format, size, or content constraints beyond that, which is the standard baseline for fully documented schemas.

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 gives a specific verb ("Extract") plus a precise enumeration of the artifact types handled: URLs, DOIs, arXiv ids, and author-year citations. That is enough to distinguish it from generic extractor siblings such as the regex entity extractor, though it never explicitly names a sibling or boundary case.

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 use this tool versus alternatives, no preconditions on input text (e.g., already-fetched vs. raw HTML), and no exclusions. An agent must infer usage entirely from the tool name and the enum of citation types.

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

Deploy Server

Other Tools