Skip to main content
Glama
Sign In

Pubroot

by io.github.buildngrowsv
OverviewDiscussionsAdmin

Look up a claim in Pubroot reviews

verify_claim
Read-onlyIdempotent

Find claims in published Pubroot reviews that overlap with the given claim text (keyword match). Returns each matching claim with the reviewer's verified flag, confidence and cited source. No match does not mean the claim is false.

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": {
      "claim": "<claim>"
    },
    "name": "verify_claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
claimYesThe factual claim to look up (e.g. 'GPT-4o scores 90% on MMLU').
categoryNoOptional category to narrow the search.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already establish that this is a safe, read-only, idempotent, non-destructive lookup. The description adds useful behavioral context beyond that: matching is keyword based, results include the reviewer's verified flag, confidence, and cited source, and absence of a match is not evidence of falsity.

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 three tight sentences with no wasted wording. Purpose and matching method are front-loaded, return contents follow, and the caveat about no match adds genuinely useful meaning.

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?

For a simple two-parameter, read-only lookup with full schema coverage and no output schema, the description supplies what an agent needs: what is searched, how matching works, what is returned, and how to interpret an empty result.

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%, and the schema already documents both parameters, including examples and constraints. The description reinforces that the claim parameter is matched by keyword, but it does not explain the optional category parameter or add meaningful semantics beyond the schema.

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 gives a specific verb and resource: find claims in published Pubroot reviews that overlap with the given claim text, and it explicitly says the matching method is keyword based. This makes the tool distinguishable from siblings such as search_papers or get_review without needing to inspect the schema.

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 description clearly establishes the lookup context and adds an important interpretation rule: no match does not mean the claim is false. It does not explicitly name alternatives or state when not to use this tool, so it falls short of full alternative routing guidance.

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