Skip to main content
Glama

What SpendQuery can answer

get_catalog
Read-onlyIdempotent

What SpendQuery can answer: data coverage, metrics, dimensions (with examples and whether they apply to contracts or assistance), analyses, the QueryPlan JSON schema, planning rules and example question -> plan pairs. Call this first (no arguments): the federal catalog. section: "states" (state, county and city checkbooks in brief: each jurisdiction, their dimensions, rules and examples), "state:" (one jurisdiction in full, e.g. "state:MA"), "rules" (every planning rule), "examples" (every worked example) or "full" (everything).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionNoOmit for the federal catalog. "states" (state, county and city checkbooks in brief), "state:<CODE>" for one jurisdiction in full (e.g. "state:MA"), "rules", "examples" or "full".

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "title": "get_catalogDictOutput",
      +  "type": "object"
      +}
  2. 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, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered and the description only needs to add workflow context. It does add some: the catalog carries the QueryPlan JSON schema and planning rules, which tells the agent this precedes run_plan, and that "full" returns everything (a mild size cue). However, the section enumeration largely restates what the schema already documents, and there is no warning about response volume for "full" or repeated calls.

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?

It is front-loaded with the highest-value instruction ("call this first") and the section options are grouped logically. The one drawback is density: the section list is a long parenthetical run-on and duplicates the schema enum, so a small amount of text does not earn its place.

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?

With an output schema present there is no need to describe return values, and the annotations carry the safety profile, so the description only needs to convey purpose, call ordering and section selection — all of which it does. Nothing an agent needs in order to invoke this correctly is missing.

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 description coverage is 100% and the single `section` parameter is fully documented in-schema, including the "state:<CODE>" format and the null default. The description's paragraph on sections repeats the same values almost verbatim, adding essentially no meaning beyond the schema. Baseline 3 is the correct ceiling here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates exactly what the tool surfaces — data coverage, metrics, dimensions, analyses, the QueryPlan JSON schema, planning rules and worked examples — and labels it "the federal catalog", so an agent knows this is a metadata/discovery endpoint rather than a data query. It also implicitly separates itself from siblings such as run_plan or search_notices via "Call this first". It stops short of an explicit verb+resource statement ("Returns the catalog of…"), relying on a content inventory instead.

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?

"Call this first (no arguments)" gives an unambiguous ordering rule relative to every sibling tool, and the per-section list tells the agent which variant to request for a narrower read. There is no explicit when-not guidance (e.g. skip if you already know the schema, or avoid 'full' when context is tight), which keeps it from a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources