Skip to main content
Glama

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

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

Annotations already indicate readOnlyHint, idempotentHint, and destructiveHint. The description adds behavioral context: scoping to user identifier, and pairing with 'remember' and 'forget'. No contradictions.

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 without fluff. Each sentence adds value: action, use cases, scoping and pairing. 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?

For a simple tool with one optional parameter, no output schema, the description is complete: retrieval, listing, scoping, and pairing. No missing information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema covers the single optional parameter 'key' with description. The description adds behavioral meaning: omitting the key lists all keys, enriching the schema's coverage.

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 value saved via 'remember' or lists all keys when the key argument is omitted. It distinguishes the tool from siblings like 'remember' and 'forget' by specifying its retrieval role.

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 explains when to use (look up context stored earlier) and provides examples (ticker, address, research notes). It implies alternatives by mentioning pairing with 'remember' and 'forget', but doesn't explicitly state when not to use it. Overall, the guidance is clear.

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

All Texas 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
Disambiguation3/5

Tools are individually well-described, but there is overlapping functionality among ask_pipeworx, ask_pipeworx_grounded, and deep_research, as well as multiple prediction market tools. The detailed descriptions help, but the number of similar tools creates some ambiguity.

Naming Consistency4/5

Tool names follow a consistent snake_case pattern with descriptive prefixes (e.g., ask_pipeworx, entity_profile, polymarket_edges). There are minor deviations like 'deep_research' vs 'bet_research' but overall the naming is predictable and clear.

Tool Count2/5

The server is named 'Texas Open Data' but only 3 of 33 tools (datasets, metadata, query) are directly related to Texas open data. The remaining tools cover a much broader domain (Pipeworx ecosystem), making the tool count inappropriate for the stated purpose.

Completeness2/5

For the stated purpose of Texas Open Data, the tool surface is incomplete—only basic query and metadata capabilities are provided, lacking data management, update, or delete operations. As a general pipeworx server it might be more complete, but the name suggests Texas-specific data.

Resources