Skip to main content
Glama

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

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

Annotations provide readOnlyHint and idempotentHint; description adds scoping to identifier, behavior when key is omitted, and pairing info. 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 sentences, each adds value. Front-loaded with action. 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?

With one optional parameter and no output schema, description fully explains what the tool does, when to use it, and how it pairs with siblings. Complete.

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%, so description adds limited extra meaning beyond the parameter description. The 'omit to list all keys' is already in 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' with specific verb and resource. Distinguishes from sibling tools 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?

Explicitly says 'Use to look up context the agent stored earlier' and mentions pairing with remember and forget. Does not explicitly state when not to use, 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 Ipma 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.9/5.0
Disambiguation2/5

The ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research cluster overlaps heavily on question-routing, and the six polymarket_* tools all operate on prediction-market edges and can be confused. The ipma_*, memory, and subscription tools are distinct, but the overlapping clusters create real misselection risk.

Naming Consistency3/5

Snake_case is used throughout and there are clear prefix groups (ipma_*, ask_pipeworx, polymarket_*), but the rest mix verb-first (compare_entities, discover_tools), noun-first (entity_profile, bet_research), and bare verbs (remember, recall, forget). Readable overall, but no consistent verb_noun convention.

Tool Count2/5

36 tools is heavy, and the server name 'Ipma Pt' implies a narrow Portugal-weather service while 31 of the tools belong to a broad Pipeworx data/prediction-market platform. The scope mismatch makes the count feel bloated rather than curated.

Completeness4/5

The dominant Pipeworx domain is well covered: querying, grounded answers, deep research, entity resolution, comparison, claim validation, subscriptions, memory, and tool discovery are all present with few dead ends. Minor gaps exist (e.g., no general web search tool, thin IPMA historical/warning coverage), but agents can work around them.

Resources