Skip to main content
Glama

Unpaywall

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already indicate idempotentHint=true and destructiveHint=false. The description adds scoping by identifier and persistence duration (permanent vs 24h), which are valuable beyond annotations. Could mention overwriting behavior, but overall good.

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?

Concise, front-loaded with purpose, every sentence adds value. No wasted words. Excellent for quick comprehension.

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?

Given the tool's simplicity (two params, no output schema), the description covers purpose, usage, behavior, and companion tools thoroughly. No gaps for an agent to use correctly.

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 covers both parameters with examples. Description adds context about key-value nature and scoping, enhancing understanding beyond the schema. No missing meaning.

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 clearly states the tool saves data for later reuse, with specific examples like ticker, address, preference. It distinguishes from siblings by naming recall and forget, making the purpose explicit and actionable.

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?

Explicitly states when to use (discover something worth carrying forward) and pairs with recall and forget. Provides clear context for the agent to decide when to invoke this tool.

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

All Unpaywall 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.8/5.0
Disambiguation3/5

Several tools overlap in purpose, especially the ask_pipeworx family (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research) which all answer factual questions but differ in grounding/depth. The beta version is explicitly identical to the stable one currently, creating confusion. The Polymarket analysis tools also have overlapping scopes, though their descriptions help differentiate them. Overall, most tools have distinct roles but the heavy overlap in the query router cluster makes misselection a real risk.

Naming Consistency3/5

Tool names mix several conventions: bare verbs (remember, subscribe, forget), verb_noun (compare_entities, resolve_entity), noun_phrase (entity_profile, pipeworx_feedback), and a brand-prefixed family (ask_pipeworx*, polymarket_*). While some prefixes are consistent, the overall pattern is inconsistent and not predictable. Names are readable but do not follow a single style.

Tool Count2/5

With 33 tools, the server is heavily over-scoped for its name 'Unpaywall', which implies a narrow open-access search utility. Even though the actual functionality is broad, the tool count is excessive and will overwhelm agents. Many tools (llms_txt generation, dependency scanning, memory) are unrelated to the core data-query function.

Completeness4/5

For the actual domain revealed by the descriptions—a comprehensive data research and prediction-market gateway—the tool surface is quite complete: it covers discovery, retrieval, grounding, entity resolution, comparison, validation, subscriptions, memory, and prediction-market analysis. Minor gaps exist (e.g., no subscription update tool, no direct tool to list all data packs), but agents can work around them. If the domain is strictly 'Unpaywall/open access', it's severely incomplete, but the descriptions clearly indicate a broader scope.

Resources