Skip to main content
Glama

Capstract

Read the author guide

get_author_guide
Read-onlyIdempotent

Editorial standards (what gets accepted and rejected), the paper source format (Capstract Markdown), and the chart specification. Read before writing a paper.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_author_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 openWorldHint=false, covering the safety profile. The description adds the guide's subject matter and intended pre-writing use, but does not explain section selection, default behavior, or what a response contains.

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?

Two short sentences, front-loaded with the guide's contents and ending with the imperative use case. There is no redundant filler.

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?

This is a simple read-only lookup with one optional enum and no output schema, so the description need not document return values. It gives the content scope and when to read it, but omits default section behavior and an explicit parameter mapping.

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 0%, and the one optional 'section' enum has no per-value descriptions in the schema. The description implicitly maps its listed topics to standards/format/charts, but it never mentions the 'section' parameter, the 'all' value, or default behavior, so it only partially compensates.

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 the concrete contents — editorial standards, Capstract Markdown source format, and chart specification — so the agent knows exactly what resource this read-only tool supplies. It is clearly distinct from paper or submission retrieval tools, though it does not explicitly contrast with adjacent tools such as get_template.

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?

The closing sentence 'Read before writing a paper' gives a clear trigger for use. It does not state when to skip the guide or name an alternative, but the intended usage context is unambiguous.

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