Skip to main content
Glama

Bnm My

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

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

Annotations already declare readOnlyHint and idempotentHint. Description adds scoping ('Scoped to your identifier') and explains the listing behavior when key omitted. Provides moderate extra context beyond 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, no fluff. Core function is in the first sentence. Every phrase earns its place (purpose, usage, scope, pairing). Exemplary conciseness.

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?

Simple tool with one optional param, good schema and annotations. The description covers all needed info: purpose, usage context, scope, dual behavior, and relationship to siblings. No gaps given the tool's complexity.

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?

Input schema has 100% coverage with description for the single parameter. Description reinforces 'omit the key argument' and clarifies the dual behavior. Baseline 3 plus added clarity justifies 4.

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?

Clearly states it retrieves a saved value or lists all keys. Explicitly differentiates from sibling 'remember' (save) and 'forget' (delete). The verb+resource combination is precise.

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 says 'Use to look up context the agent stored earlier' and pairs with 'remember' and 'forget'. The description gives clear context and points to alternatives, fulfilling both when-to-use and when-not-to-use guidance implicitly.

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

All Bnm My 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

Many tools occupy clearly different niches, but ask_pipeworx and ask_pipeworx_beta are currently identical, ask_pipeworx_grounded and deep_research heavily overlap the same router concept, and bet_research/polymarket_edges/polymarket_arbitrage all target similar 'find an edge' territory. An agent would need to read very long descriptions carefully to avoid selecting the wrong tool.

Naming Consistency4/5

Names are consistently lowercase snake_case and usefully grouped by prefixes like bnm_, polymarket_, and pipeworx_, which makes the set fairly scannable. However, conventions mix verb-first names (ask_, discover_, resolve_, validate_) with noun-phrase names (entity_profile, recent_alerts, recent_changes), so it is not a uniform verb_noun pattern.

Tool Count2/5

36 tools is well beyond the typical well-scoped 3-15 tool range, and the server bundles several distinct domains: BNM data, the Pipeworx research platform, prediction-market analysis, and memory/subscription management. This breadth would be better split into separate focused servers.

Completeness4/5

The BNM-specific surface is well covered, with dedicated tools for the main series plus a generic bnm_endpoint passthrough for anything else. The broader data side is also unusually complete, with routing, grounded answers, deep research, entity resolution, profiles, comparisons, and claim verification; only minor gaps remain, such as no dedicated historical endpoint for some BNM series.

Resources