Skip to main content
Glama

Iso

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

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

Annotations already indicate readOnly=true, idempotent=true, destructive=false. Description adds scoping by identifier and behavior when key omitted, complementing annotations without 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 efficient sentences, front-loaded with core functionality, no unnecessary words or repetition.

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?

Low complexity (1 optional param). Covers both retrieval and listing, scoping, pairing with remember/forget. No output schema, but return behavior is described. Sufficient for agent to use correctly.

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 coverage is 100% with a clear description. Description repeats the schema's 'omit to list all keys' inline, adding no new semantic details 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 explicitly states the tool retrieves saved values or lists keys, with verb 'retrieve' and 'list', resource 'value' or 'keys', and distinguishes 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 clear when-to-use guidance with examples (ticker, address, notes) and mentions how to list all keys by omitting the argument. No explicit when-not-to-use, but strong positive guidance.

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

All Iso 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.6/5.0
Disambiguation3/5

Tools are mostly distinct but there is some overlap among lookup tools (ask_pipeworx, ask_pipeworx_grounded, deep_research, entity_profile) and among Polymarket tools (bet_research, polymarket_edges, polymarket_arbitrage). Agents might occasionally struggle to choose the right one.

Naming Consistency2/5

Naming is inconsistent: some use verb_noun snake_case (ask_pipeworx, compare_entities), some are single words (forget, recall, remember), and others are noun-based (compliance_catalog, entity_profile). No consistent pattern.

Tool Count1/5

With 34 tools, the count is too high for a server named 'ISO Standards'. The majority of tools are unrelated to ISO standards (e.g., Polymarket, memory, web scraping), making the scope highly inappropriate.

Completeness1/5

As an ISO standards server, the tool set is severely incomplete. Only 4-5 tools (search_standards, get_standard, compliance_catalog, open_data_files) actually deal with ISO standards. Essential operations like comparing standards or browsing revisions are missing.

Resources