Skip to main content
Glama

Us Iso Grid

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The description adds behavioral context beyond annotations: it explains persistence (authenticated users get persistent memory, anonymous sessions last 24 hours) and that it's a key-value store scoped by identifier. Annotations already indicate idempotentHint=true and readOnlyHint=false, and the description is consistent.

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?

The description is concise (4 sentences) and front-loaded with the core purpose. Every sentence adds meaningful information without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers purpose, usage, persistence behavior, and pairing with sibling tools. While it doesn't describe the return value or error conditions, the tool's simplicity and lack of output schema make this acceptable.

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?

The input schema already provides 100% coverage with descriptions for both parameters. The description adds examples of key and value content (e.g., 'subject_property', 'findings'), which is helpful but not substantial 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 uses a specific verb ('Save') and resource ('data'), clearly states the purpose is for reuse across conversations/sessions, and distinguishes from related tools (recall, forget) by mentioning them as companions.

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?

The description provides explicit context for when to use ('when you discover something worth carrying forward') and lists the companion tools (recall, forget). It lacks explicit 'when not to use' guidance, but the positive usage is clearly articulated.

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

All Us Iso Grid 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

There are multiple overlapping query tools (ask_pipeworx, ask_pipeworx_grounded, deep_research, discover_tools) that could confuse an agent about which to use. Similarly, several Polymarket tools have overlapping functions. However, descriptions are detailed enough to distinguish most, and energy grid tools are clearly separated by ISO.

Naming Consistency3/5

Tool names consistently use snake_case, but there is no uniform verb_noun pattern. Some start with verbs (ask, compare, scan), others with nouns (entity_profile, recent_alerts), and many use domain prefixes (caiso_, polymarket_). This mixed style reduces predictability.

Tool Count2/5

With 40 tools spanning unrelated domains (AI visibility, energy grids, prediction markets, memory, SEO, subscriptions), the server feels overloaded. A typical focused server would have 3-15 tools; this range indicates scope creep and lack of coherence.

Completeness2/5

The server covers multiple domains but lacks depth in each. For example, energy grid tools cover only three ISOs (CAISO, ERCOT, NYISO), missing many others. The prediction market tools are extensive but incomplete without real-time price updates. The general query tool 'ask_pipeworx' tries to cover everything, but the overall surface is uneven and has notable gaps.

Resources