Skip to main content
Glama

Treasury Fiscal

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

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

Annotations provide idempotentHint=true but no persistence info; description adds scoping by identifier, persistence per authentication status, and 24-hour retention for anonymous sessions, going 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Concise and front-loaded with purpose, but could be slightly more structured (e.g., bullet points for examples) without losing information.

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?

No output schema needed; description explains storage behavior, scope, and related tools, making it complete for a simple key-value store tool.

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 covers both parameters; description adds example keys and value type context, but does not list specific valid key naming conventions beyond examples.

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 the agent will need to reuse later', clearly distinguishing it from sibling tools like recall 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use ('when you discover something worth carrying forward'), provides examples, and directs pairing with recall/forget.

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