Skip to main content
Glama

Usaspending

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

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description reinforces safe behavior. It adds value by disclosing scoping (anonymous IP, key hash, account ID) and pairing expectations, which go beyond what annotations provide.

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?

Description is only three sentences, with the most important action and usage upfront. Every sentence adds value: action, use cases, scoping, and pairing. No unnecessary words.

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 simple one-param tool with annotations covering safety and idempotency, the description fully covers behavior, scoping, and usage pattern. No output schema needed; return is implied. All signals (completeness, sibling context) are well addressed.

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 parameter description already stating 'omit to list all keys'. The description does not add new parameter-level meaning beyond the schema, so baseline 3 is appropriate.

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?

Description clearly starts with verb 'Retrieve' and specifies two modes: get a specific value by key or list all keys. It distinguishes itself from sibling tools 'remember' and 'forget' by explaining the pairing, and provides concrete use cases like ticker or address lookup.

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?

Description explicitly states when to use ('to look up context the agent stored earlier') and advises against re-deriving info. It scopes usage to identifier types. While it doesn't list alternatives explicitly, the sibling context and mention of 'remember'/'forget' provide clear guidance.

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

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

ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are essentially the same router with different output modes, and ask_pipeworx_beta is currently identical to ask_pipeworx. There is also meaningful overlap between entity_profile, compare_entities, recent_changes, validate_claim, and the USAspending profile/search tools.

Naming Consistency3/5

All names are lower_snake_case with useful prefixes like ask_, polymarket_, and usa_, which helps grouping. However, the underlying convention is mixed: some are verb+object, some are noun phrases, and some are bare verbs, so there is no uniform verb_noun pattern.

Tool Count2/5

38 tools is well beyond the heavy range, and most of them are unrelated to USAspending: Polymarket betting, npm dependency checks, AI visibility, memory storage, and meta-tools. The actual USAspending-specific surface is only about seven tools, making the server feel bloated and unfocused.

Completeness3/5

The federal-contract cluster covers award search, recipient/incumbent profiles, expiring awards, and spending by agency/category/trend, which handles the main contracting questions. Missing award-detail retrieval, grants/assistance coverage, and open-solicitation lookup, which usa_expiring_awards explicitly punts to external samgov/govcon tools.

Resources