Skip to main content
Glama

Bpstat Pt

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.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and the description is fully consistent. It adds value by explaining the scoping to anonymous IP, BYO key hash, or account ID, which is not in annotations.

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 sentences: first states core function, second gives use cases, third adds scope and pairing. No wasted words, front-loaded with purpose.

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?

With single optional parameter, 100% schema coverage, and no output schema, the description fully explains behavior when key is omitted (list keys) and scoping. Complete for this simple tool.

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 coverage is 100% with description 'Memory key to retrieve (omit to list all keys)'. The tool description reinforces this and adds concrete examples (ticker, address, research notes), enhancing semantic understanding 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 retrieves a saved value or lists all keys, with specific verb ('retrieve') and resource ('value previously saved via remember'). It distinguishes from sibling tools 'remember' and 'forget' by explicitly naming them in the context.

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?

The description provides explicit usage context: looking up stored context like ticker, address, research notes. It also indicates when to omit the key argument (list keys) and pairs with remember/forget for a complete workflow.

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

All Bpstat Pt 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

Multiple tool clusters are nearly indistinguishable: ask_pipeworx and ask_pipeworx_beta are explicitly documented as currently identical, scan_competitor_ai_presence is a thin wrapper over ai_visibility_check, and the five polymarket_* tools (edges, edge_tracker, arbitrage, fill_risk, kalshi_spread) share heavily overlapping edge-detection/fill-analysis concerns. entity_profile and recent_changes also both fan out to the same SEC/news/patents sources, so an agent must read full descriptions to avoid misselection.

Naming Consistency3/5

The dominant pattern is imperative verb_first (list_datasets, get_dataset, resolve_entity, validate_claim, scan_dependency, subscribe), but there are notable deviations: noun-phrase names like entity_profile, recent_alerts, recent_changes, bet_research, and deep_research; the ask_pipeworx brand family sits awkwardly beside get_/search_ verbs; and the polymarket_* prefix family forms yet another convention. Names are readable and mostly self-explanatory, but no single consistent scheme is followed.

Tool Count2/5

At 35 tools, this exceeds the 'too many (25+)' threshold, and the bloat is compounded by the server's nominal identity: despite being named 'Bpstat Pt' (Banco de Portugal statistics), only about 5 tools (list_domains, list_datasets, get_dataset, get_series_metadata) actually serve that domain. The other 30 tools span unrelated subsystems — Polymarket betting, npm dependency scanning, AI visibility audits, generic memory, and subscriptions — suggesting several products bundled into one server.

Completeness3/5

For the broader data-gateway interpretation, the lifecycle is well covered: discovery (discover_tools, suggest_questions), query (ask_pipeworx), grounded verification (ask_pipeworx_grounded, validate_claim), deep research (deep_research), profiles/comparisons (entity_profile, compare_entities), monitoring (recent_changes, subscribe/recent_alerts), and memory (remember/recall/forget). However, for the nominal Bpstat statistical domain there is no keyword search over series or datasets — navigation requires knowing domain/dataset ids in advance — and the extreme scatter across unrelated domains leaves each subsystem only partially developed.

Resources