Skip to main content
Glama

Imf Portwatch

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

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

Discloses scoping to identifier (anonymous IP, BYO key hash, account ID) and relationship to remember/forget, adding value beyond annotations which already declare readOnlyHint and destructiveHint. 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 with zero wasted words. Front-loaded with core purpose, followed by usage and scoping details. Highly efficient.

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 single optional parameter, no output schema, and annotations covering safety, the description provides complete guidance: purpose, usage, scoping, and sibling relationships. No gaps for this complexity level.

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 clear property description. The description reinforces the optional key behavior and adds context like 'omit the key argument' and pairing with other memory tools, providing slight extra value beyond schema alone.

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-resource pairing. It distinguishes from siblings 'remember' and 'forget' by explicitly mentioning pairing, making purpose unambiguous.

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 scenario: 'Use to look up context the agent stored earlier' and how to list all keys (omit key argument). Does not include explicit when-not-to-use or alternative tools, but context is clear and sufficient for typical use.

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

All Imf Portwatch 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

A4.2/5.0
Disambiguation4/5

Most tools have clear distinct purposes, but the three ask_pipeworx variants (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) are very similar, and there is some overlap between bet_research and polymarket_edges. Overall, the majority are well-differentiated.

Naming Consistency5/5

Tool names follow a consistent snake_case verb_noun pattern with only minor deviations (e.g., 'chokepoints_list' vs 'chokepoint_daily_traffic'). The naming convention is predictable and clear.

Tool Count2/5

At 37 tools, the surface is overly large for a focused server. Many tools are meta-tools that could have been consolidated, and the count exceeds the recommended range (25+), making it feel heavy and unwieldy.

Completeness5/5

The server covers maritime chokepoints comprehensively (list, status, daily, compare, disruptions), and the Pipeworx-based tools provide broad coverage across financial, drug, prediction market, and general query domains. There are no obvious gaps for the stated scope.

Resources