Skip to main content
Glama

CiteStamp

by com.citestamp
OverviewDiscussionsAdmin

Edges about

edges_about
Read-onlyIdempotent

Every edge touching the given work in either direction, each tagged asserted|inferred with attribution and provenance. Use when a user asks 'what is known about this paper's citations' or wants the whole neighbourhood in one call. Paged.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum edges to return per tier (default 100, max 1000). Well-cited works have thousands; the response reports has_more and inferred_total so you can tell a page from the whole answer.
offsetNoHow many edges to skip, for paging. Advance by the LIMIT you asked for, not by the number of results you got back — duplicates are removed after the window is taken, so a page can return fewer rows than it consumed. Keep going while has_more is true.
identifierYesDOI, arXiv id, OpenAlex id, or internal claim id
asserted_onlyNoIf true, restrict to human-signed (asserted) edges. If false (default), return both asserted and machine-inferred edges.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 100,
+  "description": "Maximum edges to return per tier (default 100, max 1000). Well-cited works have thousands; the response reports has_more and inferred_total so you can tell a page from the whole answer.",
+  "maximum": 1000,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "How many edges to skip, for paging. Advance by the LIMIT you asked for, not by the number of results you got back — duplicates are removed after the window is taken, so a page can return fewer rows than it consumed. Keep going while has_more is true.",
+  "minimum": 0,
+  "type": "integer"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so safety is covered. The description adds real behavioral context beyond that: results are tiered as asserted vs inferred, each carries attribution and provenance, and the operation is paged — all of which shape how an agent interprets output. It stops short of describing ordering or dedup mechanics, which live in the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences plus a terse 'Paged.' fragment; the core scope statement is front-loaded and nothing is padded. The trailing one-word fragment is slightly abrupt but efficient rather than wasteful.

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 paged read tool with no output schema, the description covers the key concepts an agent needs (bidirectional neighbourhood, asserted vs inferred tiers, paging) and the schema handles pagination mechanics. It could say more about result ordering or the shape of an edge record, but nothing critical 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?

Schema description coverage is 100% and the parameter descriptions are unusually rich (limit tiers, offset paging semantics, duplicate removal, has_more). The description only adds the vague word 'Paged', so it contributes little beyond the schema — baseline 3 is appropriate.

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+resource with scope: 'every edge touching the given work in either direction', and adds the tiering ('asserted|inferred with attribution and provenance'). It implicitly contrasts with siblings by offering the 'whole neighbourhood in one call' versus the narrower references_of/what_cites/what_refutes/what_supports, but it never names them, so differentiation rests on inference.

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?

Gives a concrete trigger ('Use when a user asks "what is known about this paper's citations" or wants the whole neighbourhood in one call'), which is clear context for selection. It does not explicitly state when to prefer a narrower sibling instead (e.g. when the user only wants cited-by edges), so no exclusion guidance.

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

All CiteStamp toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources