Skip to main content
Glama

Pubmed

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. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate a non-destructive write (readOnly=false, destructive=false) and idempotence. The description adds persistence details (authenticated vs anonymous 24-hour retention) and scoping by identifier, enhancing transparency, though it doesn't address overwrite behavior or limits.

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?

Four sentences, each covering a distinct aspect: purpose, usage, persistence, and related tools. Slightly longer than minimal but well-organized and free of redundancy.

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 simple store tool with full schema and annotations, the description covers purpose, usage, persistence, and sibling relationships. Minor omissions like overwrite behavior or value size limits don't significantly impair understanding.

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 covers both key and value with examples, so baseline is 3. Description adds the concept of scoping by identifier but doesn't provide parameter-specific detail 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 clearly states the tool saves data for later reuse, specifying a key-value pair. It also distinguishes itself from recall and forget by naming them as complementary tools.

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 conditions for use ('when you discover something worth carrying forward') with concrete examples, and mentions pairing with recall/forget for retrieval/deletion, establishing when to use alternatives.

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

All Pubmed 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
Disambiguation2/5

Several tool groups overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all answer questions against the same data sources, and the Polymarket suite (polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread, bet_research) has unclear boundaries. An agent would struggle to pick the right one.

Naming Consistency2/5

Names mix verb phrases (search_pubmed, get_abstract, validate_claim) with noun phrases (entity_profile, polymarket_arbitrage, bet_research) and bare verbs (remember, forget). The ask_pipeworx family uses a non-standard prefix, and there's no consistent verb_noun pattern across the set.

Tool Count2/5

37 tools is far too many for a server that presents as a PubMed tool. The majority are unrelated to biomedical literature (memory, subscriptions, prediction markets, real estate, etc.), making the surface feel bloated and unfocused.

Completeness4/5

The PubMed-specific tools form a complete lifecycle: search, citation metadata, abstract, full text, forward citations, and related articles. However, the server's broader domain is unclear and unevenly covered — many non-PubMed areas have partial coverage.

Resources