Skip to main content
Glama

Treasury Fiscal

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. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "key": "user_research_topic"
+  },
+  {}
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare readOnlyHint, idempotentHint, and destructiveHint. The description adds scoping details (anonymous IP, BYO key hash, or account ID) and the behavior of omitting the key argument. 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?

The description is concise (two sentences) and front-loaded with the main purpose. Every sentence adds value with no unnecessary fluff.

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 tool's simplicity, annotations cover safety, and the description provides clear instruction on usage. Even without an output schema, the return behavior (value or list) is implied sufficiently for an agent.

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%, and the description adds meaning by explaining that omitting the key lists all keys. This provides usage context beyond the schema's parameter description.

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. It uses specific verbs and resources, and 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?

The description explains when to use the tool (to look up stored context without re-deriving) and implies alternatives (remember to save, forget to delete). It lacks explicit when-not-to-use but provides clear context.

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

All Treasury Fiscal 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
Disambiguation2/5

Most of the surface is dominated by overlapping meta-tools (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research) plus paired helpers (discover_tools/suggest_questions, ai_visibility_check/scan_competitor_ai_presence), so an agent can easily pick the wrong one. The seven treasury_* tools are clearly distinct, but they are a small island in a much larger ambiguous set.

Naming Consistency3/5

Names are broadly snake_case and family-prefixed (treasury_*, polymarket_*, pipeworx_*), which helps, but the pattern is not consistently verb_noun: ask_pipeworx, bet_research, entity_profile, deep_research, search_within, and recent_changes mix verb, noun, and product-specific naming styles. Within families it is readable, but across the whole set it is inconsistent.

Tool Count2/5

37 tools is too many for a server whose label is 'Treasury Fiscal'; only about six tools are treasury-specific and the rest are unrelated research, betting, memory, and subscription utilities. This is well into the 25+ heavy range and would make tool selection expensive and error-prone.

Completeness2/5

For a Treasury/Fiscal server the surface is thin: debt, receipts, customs duty, average rates, exchange rates, and net cost cover only a slice of Treasury data. Missing obvious components such as daily yield curves, auction calendars/results, federal outlays/spending by agency or function, and tax or appropriations data; the broad ask_pipeworx router softens but does not fill these as first-class tools.

Resources