Skip to main content
Glama
Sign In

Pubroot

by io.github.buildngrowsv
OverviewDiscussionsAdmin

Find related Pubroot papers

get_related_work
Read-onlyIdempotent

List Pubroot papers related to a query or to a given paper ID, ranked by keyword overlap.

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_related_work"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoTopic or question to find related work for.
paper_idNoOptional paper ID (e.g. '2026-042') to find related work for.

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value by disclosing the ranking mechanism (keyword overlap), which tells the agent results are lexical rather than semantic. It does not disclose result count limits, pagination, or the empty-parameter behavior.

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 sentence that front-loads the resource and input modes and ends with the ranking rule. Every clause carries information; nothing is padded.

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 two-parameter read tool with rich annotations and no output schema, this is close to adequate. Gaps remain around result-set size, ranking ties, and the all-defaults case, which matter for an agent deciding how to call it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, which sets a baseline of 3, and the description adds the meaningful relational fact that query and paper_id are alternative entry points rather than combined filters. It still leaves open what an empty query and empty paper_id produce.

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?

States a specific verb ('List') and resource ('Pubroot papers') plus the two input modes (query or paper ID) and the ranking basis ('keyword overlap'). This is clear enough to distinguish it from search_papers, though the description never names that sibling explicitly.

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 'related to a query or to a given paper ID', which tells the agent the retrieval intent. There is no explicit when-to-use guidance versus search_papers, and no note on what happens if both parameters are omitted or supplied together.

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