Skip to main content
Glama
Sign In
paper-mcp

paper-mcp

by Friedemann12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List arXiv categories

list_categories
Read-onlyIdempotent

List arXiv category codes and display names. Optionally filter by prefix to narrow to a group like cs or math.

Instructions

List known arXiv category codes and their display names.

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

Input Schema

NameRequiredDescriptionDefault
prefixNoOptional group filter, e.g. 'cs', 'math', 'q-bio', 'stat'.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, covering safety. The description adds behavioral context by specifying that the tool returns category codes and display names, which tells the agent what to expect. It does not disclose other traits like pagination, but it is consistent and adds value beyond 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?

The description is a single, front-loaded sentence that states exactly what the tool does without any waste. Every word earns its place.

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

Completeness5/5

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

Given the simplicity of the tool, the schema fully documents the optional parameter, annotations declare the safe and idempotent nature, and the description conveys the core purpose. An output schema exists, so return values need not be described. Nothing important is missing.

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?

The input schema has 100% coverage, describing the optional prefix parameter with examples ('cs', 'math', etc.). The tool description itself does not add parameter details, so the schema carries the load. Baseline 3 is appropriate.

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?

The description uses a specific verb ('List') and clearly identifies the resource ('arXiv category codes') and the output content ('display names'). This distinguishes it from sibling tools like search_papers and get_paper, which are search/retrieval operations.

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?

The description implies the tool is for retrieving category metadata but does not explicitly state when to use it versus alternatives or mention any exclusions. There is no guidance on when to use the optional prefix filter, though the schema provides examples.

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