StatsPAI

bibtex

Read-only

Look up verified BibTeX entries by citation key from StatsPAI's paper.bib; unknown keys return an empty entry with close-match suggestions.

Instructions

Return verified BibTeX entries from paper.bib (StatsPAI's single source of truth for citations). Pass one or more bib keys (e.g. 'callaway2021difference'). NEVER invent citations -- call this tool instead. Unknown keys return an empty entry plus a list of close matches.

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": {
      "keys": "<keys>"
    },
    "name": "bibtex"
  }
}

Input Schema

Name	Required	Description	Default
`keys`	Yes	Bib keys to look up. Most estimators advertise their key in agent_card.reference.
`detail`	No	Payload depth; agent is the fullest.	agent
`data_id`	No	Data handle (d_...) from load_data; replaces data_path.
`data_csv`	No	Small inline table as CSV text.
`as_handle`	No	Cache the fit and return its result_id.
`data_path`	No	Absolute path of a data file on the server.
`result_id`	No	Handle of an earlier fit made with as_handle=true.
`data_records`	No	Small inline table as row objects.
`max_output_bytes`	No	Result byte budget (default 262144; 0 = none).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 12, 2026

TDQS

A4/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 safety is covered. The description adds genuinely useful behavior: entries are 'verified' and unknown keys yield an empty entry plus close matches, which tells the agent how failures look. It says nothing about output size, detail levels, or the role of the assorted data/handle parameters, so it goes only modestly beyond the annotations.

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?

Three short sentences, front-loaded with the purpose, then the required input, then the anti-fabrication rule and failure behavior. Every sentence carries information the agent needs.

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 explain return values, and it covers purpose, input, and unknown-key behavior adequately. The one gap is that nine parameters, including several data/handle options that look unrelated to a bib lookup, are left entirely to the schema with no orienting comment.

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 the schema already documents every parameter including detail, data_id, and max_output_bytes. The description adds an example key format ('callaway2021difference') and reinforces that keys come from estimator metadata, but leaves the many boilerplate-looking data and result-handle parameters unexplained beyond the schema.

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?

States a specific verb and resource ('Return verified BibTeX entries from paper.bib') and pins down its role as the single source of truth for citations. An agent can tell this is a citation-lookup utility and not an estimator or audit tool among the siblings.

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

Usage Guidelines4/5

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

Gives an explicit usage directive: 'NEVER invent citations -- call this tool instead,' which defines when the tool must be used. It does not name any sibling tools or describe exclusions relative to them, keeping it short of a full when/when-not treatment.

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