Skip to main content
Glama
Sign In

Pubroot

by io.github.buildngrowsv
OverviewDiscussionsAdmin

Get a paper's index entry

get_paper
Read-onlyIdempotent

Return the published index metadata (title, author, category, abstract, score, badge, status, links) for a Pubroot paper ID.

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_idYesThe paper ID (e.g. '2026-042').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare the operation as read-only, idempotent, non-destructive, and closed-world. The description adds useful context by enumerating the returned metadata fields, but it does not describe error behavior for invalid or unpublished IDs, nor any access constraints beyond the identifier format.

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?

A single front-loaded sentence states the action, resource, and returned fields with no redundant wording. Every part earns its place.

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?

For a one-parameter read-only lookup with annotations covering safety traits, the description is largely complete. It identifies the resource and enumerates return fields; only edge-case behavior and sibling distinction are left implicit.

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 coverage is 100%, including the paper_id pattern and example, so the schema already fully documents the only parameter. The description reiterates the paper ID concept but adds no format or semantic detail beyond the schema.

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 gives a specific verb and resource: return published index metadata for a Pubroot paper ID, and lists the metadata fields returned. It is clear what the tool does, but it does not explicitly differentiate itself from siblings such as search_papers or get_review.

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 implied by 'for a Pubroot paper ID', indicating a direct ID lookup. However, there is no explicit guidance on when to use this versus search_papers, get_review, or other siblings, and no stated exclusions or prerequisites.

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

All Pubroot toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources