Skip to main content
Glama

Utah Open Data

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
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds context about scoping to an identifier and pairing with other tools, but does not significantly expand 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?

The description is three sentences, front-loading the core purpose, and every sentence adds value without redundancy. It is efficiently structured and easy to parse.

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 the simple tool with one optional parameter and no output schema, the description provides sufficient context for correct usage, including scope and usage patterns.

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 description for the key parameter. The description adds additional meaning by explaining the key is a saved value and that omitting it lists all keys, complementing 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 clearly states the tool retrieves saved values or lists all keys, using specific verbs 'retrieve' and 'list'. It distinguishes from siblings 'remember' and 'forget' by explaining the retrieval function.

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 explicitly states when to use the tool: to look up previously stored context without re-deriving. It also mentions pairing with 'remember' and 'forget'. However, it lacks explicit guidance on when not to use it or alternative tools.

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

All Utah Open Data 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

The toolset contains several near-duplicate clusters: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route the same kinds of questions, and the six polymarket tools have heavily overlapping scopes. An agent would frequently struggle to pick the right variant despite the detailed descriptions.

Naming Consistency4/5

Names consistently use lowercase snake_case with a verb-first or domain-prefixed pattern (ask_pipeworx, resolve_entity, validate_claim, polymarket_arbitrage). Minor deviations like bare nouns (datasets, metadata) are acceptable but not perfectly uniform.

Tool Count2/5

34 tools is far beyond what a Utah Open Data server needs; only 3 tools actually relate to the named domain. The rest form a sprawling general-purpose Pipeworx/prediction-market platform, making the surface feel bloated for its stated purpose.

Completeness3/5

For the actual Utah Open Data catalog, datasets/query/metadata is a complete read-only surface. But for the broader Pipeworx functionality the set actually delivers, there are odd gaps (no account management beyond subscriptions) and many irrelevant tools, so overall coverage is uneven.

Resources