Skip to main content
Glama

Pdbe

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)

Schema Changelog

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

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint true. Description adds value by explaining scoping to user identifier and pairing with remember/forget. No contradiction.

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?

Three concise sentences front-loaded with main action. Every sentence adds value. No wasted words.

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 one optional parameter, no output schema, and robust annotations, the description fully covers purpose, usage, scoping, and pairing with siblings. Complete for a simple retrieval tool.

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% for the single optional parameter, and the description restates the same behavior (omit to list all keys). No additional meaning beyond 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?

Description clearly states 'Retrieve a value previously saved via remember, or list all saved keys', using specific verbs and resource. Differentiates from siblings like 'remember' and 'forget'.

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?

Provides explicit usage context: 'look up context the agent stored earlier' with examples. Mentions scoping and pairing with remember/forget. No explicit when-not, but context is clear.

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

All Pdbe 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

B3.3/5.0
Disambiguation2/5

Many tools overlap in purpose: ask_pipeworx, ask_pipeworx_grounded, ask_pipeworx_beta, and deep_research all perform similar data lookups with slight variations. Prediction market tools (bet_research, polymarket_arbitrage, polymarket_edges) also overlap. Only the three PDBe-specific tools are clearly distinct, but overall the set is confusing.

Naming Consistency1/5

Tool names follow no consistent pattern: some are verb_noun (ask_pipeworx, get_molecules), others are noun_verb (ai_visibility_check), or have mixed conventions (generate_llms_txt, uniprot_mappings). The variety of verbs (ask, bet, compare, discover, generate, get, list, recall, remember) makes it hard to predict tool names.

Tool Count2/5

With 34 tools, the server is overstuffed for a single domain. It mixes PDBe-specific tools (3) with a large set of general-purpose data tools, prediction market tools, subscriptions, and memory tools. This bloat suggests the server should be split into focused services.

Completeness1/5

For the stated PDBe domain, only three tools exist (get_molecules, get_summary, uniprot_mappings), missing essential operations like search, download, or advanced queries. The server's overall purpose is unclear, and it feels like a random collection of tools rather than a coherent API.

Resources