Skip to main content
Glama

Treasury Fiscal

by io.github.pipeworx-io

Treasury Receipts

treasury_receipts
Read-onlyIdempotent

Get US government receipts by source: individual income tax, corporate tax, excise taxes, customs duties, and more.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of records to return (default 12)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesNumber of records returned
recordsYesGovernment receipts by source
descriptionYesDescription of the data
total_availableYesTotal available records in the API

Schema Changelog

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

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of records returned",
+      "type": "number"
+    },
+    "description": {
+      "description": "Description of the data",
+      "type": "string"
+    },
+    "records": {
+      "description": "Government receipts by source",
+      "items": {
+        "properties": {
+          "classification": {
+            "description": "Classification description or code",
+            "type": "string"
+          },
+          "current_month_amt": {
+            "description": "Current month receipt/outlay amount",
+            "type": "number"
+          },
+          "fiscal_year_amt": {
+            "description": "Fiscal year receipt/outlay amount",
+            "type": "number"
+          },
+          "line_code": {
+            "description": "Line code number",
+            "type": "string"
+          },
+          "record_date": {
+            "description": "Date of the record",
+            "type": "string"
+          },
+          "table_name": {
+            "description": "Table name",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_available": {
+      "description": "Total available records in the API",
+      "type": "number"
+    }
+  },
+  "required": [
+    "description",
+    "count",
+    "total_available",
+    "records"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 12
+  },
+  {
+    "limit": 36
+  }
+]
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint true, so the agent knows it's safe and repeatable. The description adds that it returns receipts by source, but does not disclose any additional behavioral traits like pagination, data recency, or whether the 'limit' parameter caps results.

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?

Single sentence, 17 words, front-loaded with the core action. Every word is necessary.

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?

Given the tool's simplicity (one optional parameter, output schema exists), the description sufficiently explains what the tool does. It could mention the default limit or how data is ordered, but the output schema covers return values.

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?

Schema coverage is 100% with the 'limit' parameter described. The description adds no parameter-specific meaning beyond what the schema already provides (default 12, records to return).

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 it retrieves US government receipts by source, listing specific examples (individual income tax, corporate tax, etc.). This differentiates it from sibling tools like treasury_customs_revenue or treasury_avg_interest_rates.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

No explicit guidance on when to use this tool versus alternatives. The description implies it covers overall receipts, but does not mention when to prefer it over sibling tools like treasury_debt or treasury_exchange_rates.

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