Skip to main content
Glama

Capstract

Get an announced paper

get_paper
Read-onlyIdempotent

Metadata and abstract of an announced paper, optionally with its paper source when it was typeset by capstract.

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": {
      "paper_id": "<paper_id>"
    },
    "name": "get_paper"
  }
}

Input Schema

NameRequiredDescriptionDefault
paper_idYes
include_sourceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds genuinely new behavioral context: the payload is metadata plus abstract, with source included only under a specific condition. It does not say what happens when the paper is not announced or not found.

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?

A single compact sentence with the core payload front-loaded and the conditional qualifier trailing it; no filler. It is technically a fragment lacking a verb, but that costs nothing here.

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

Completeness3/5

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

With no output schema, the description reasonably sketches the return payload, which is the main thing an agent needs. It leaves gaps on the ID format and on failure behavior for unannounced or nonexistent papers, which matter for a lookup tool.

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%, so the description must carry the parameter burden. It partially compensates for include_source by explaining that the source is returned 'optionally when it was typeset by capstract', but it says nothing about paper_id, whose regex-constrained format is documented nowhere else.

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 names a concrete resource (an announced paper's metadata and abstract) and states the conditional extra (paper source when typeset by capstract), so an agent knows what it retrieves. It is written as a noun phrase rather than a verb, and it does not explicitly distinguish itself from search_papers, but the 'announced paper' scoping keeps the purpose unambiguous.

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?

Usage is only implied: an agent can infer this is the way to fetch a single known paper by ID, versus search_papers for discovery. There is no explicit when-to-use statement, no mention of the precondition that the paper must already be announced, and no routing to alternatives.

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