Skip to main content
Glama

Capstract

Get a template's example paper

get_template
Read-onlyIdempotent

A complete example paper for a template, as a paper source you can study or adapt. Examples show every feature and the expected quality bar.

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": {
      "template_id": "<template_id>"
    },
    "name": "get_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
template_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely new behavioral context by characterizing the payload itself: it is a complete paper, it exercises every template feature, and it sets the expected quality bar. It does not state format (raw LaTeX?) or size, which keeps it below a 5.

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, front-loaded with what the tool returns, with no redundant restatement of the name. The second sentence ('every feature and the expected quality bar') is slightly promotional but still carries evaluative information an agent can act on.

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?

For a single-parameter, read-only fetch with no output schema, the description covers what comes back and why it is useful. It leaves gaps on output format, document size, and how to pick among the seven enum values, which matter for an artifact of this kind.

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 one required parameter with 0% schema description coverage; only the enum of seven template IDs is self-documenting. The description says the example is 'for a template', which implicitly matches template_id, but it adds no meaning about what distinguishes article, mlconf, sigconf, physrev, nature, or clinical, so an agent cannot choose confidently without another tool.

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 title and first sentence state a specific resource: a complete example paper belonging to a template, delivered as paper source. That distinguishes it reasonably well from get_paper (a presumably real submission) and get_author_guide (guidance rather than an artifact). It never names a sibling or a verb like 'retrieve', so the differentiation is implied 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?

'as a paper source you can study or adapt' implies the use case (learning template conventions, bootstrapping a draft), but there is no explicit when-to-use versus get_author_guide or get_paper, and no note about calling list_templates first to discover valid template IDs. Usage is inferable but not guided.

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