Skip to main content
Glama

Opencitations

by io.github.pipeworx-io

Recall

recall
Read-onlyIdempotent

Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous IP, BYO key hash, or account ID). Pair with remember to save, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoMemory key to retrieve (omit to list all keys)

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds valuable context about scoping ('anonymous IP, BYO key hash, or account ID') and the listing behavior when key is omitted, which is beyond annotation coverage.

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?

Description is three sentences, front-loaded with the core action, and every sentence earns its place without redundant phrasing.

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 one-parameter tool with strong annotations and no output schema, the description covers purpose, usage, scoping, and complementary actions fully. No significant gaps remain.

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 property description already states 'omit to list all keys.' The description adds no further parameter detail beyond what the schema provides, so 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 states a specific verb and resource: 'Retrieve a value previously saved via remember, or list all saved keys.' It clearly distinguishes itself from siblings by naming remember and forget as complementary tools, and explains the optional key behavior.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use context: 'Use to look up context the agent stored earlier... without re-deriving it from scratch.' It elaborates on scenarios (target ticker, address, research notes) and pairs with remember/forget, giving clear guidance on the workflow.

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

All Opencitations toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation2/5

Multiple tools overlap heavily: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical router variants, and entity_profile/compare_entities/recent_changes/ai_visibility_check all inspect companies from overlapping angles. The six Polymarket tools form a tightly-overlapping mini-domain that further crowds the surface.

Naming Consistency3/5

All names are snake_case, but verbs are inconsistently used: many tools are noun phrases (citation_count, entity_profile, polymarket_edges) while others start with verbs (ask_pipeworx, compare_entities, validate_claim). Some prefixes like ask_* and polymarket_* help, but the overall verb/noun pattern is not coherent.

Tool Count2/5

37 tools is well above the typical 3–15 tool scope, and several are redundant variants (three ask_pipeworx modes) or hyper-specific sub-tools (six Polymarket tools). The server name suggests a focused citation service, but only six tools actually address citations, leaving the set bloated with unrelated data query and memory utilities.

Completeness3/5

For a general data-query gateway, the surface is quite broad and covers lookup, profiling, comparisons, subscriptions, and memory. But as an OpenCitations server it lacks a way to discover papers by topic and the breadth of the other domains is unwieldy and unowned—so notable gaps exist in any plausible stated purpose.

Resources