Skip to main content
Glama
Sign In

FedWatch — Federal Funding & Lien Watcher

by io.github.jabbertones-cloud
OverviewDiscussionsAdmin

grants_search_programs

Search the SAM.gov Assistance Listings program catalog (the programs behind the grants — by agency and program number). Catalog data: use grants_search for live deadlines.

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": "grants_search_programs"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNoMax results (default 25)
keywordNoProgram keyword, e.g. 'rural health'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description still signals the key behavioral distinction: this returns catalog data, not live deadlines. It implies a safe read-only search operation, but does not discuss result limits or pagination behavior beyond the schema default.

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?

Two compact sentences, front-loaded with the core purpose and immediately followed by the sibling alternative. No filler.

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?

For a simple two-parameter search tool with no output schema, the description gives enough: source system, data type, and the alternative for live deadlines. No critical invocation details are 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 coverage is 100%, so the schema already defines keyword and size. The description adds context about agency/program-number lookup, but does not provide parameter syntax or format guidance beyond what the schema supplies.

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?

States a specific verb and resource: search the SAM.gov Assistance Listings program catalog. It also clarifies what the catalog contains (programs behind grants) and distinguishes it from grants_search, which handles live deadlines.

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 routes live-deadline searches to grants_search and establishes this tool as the catalog-search option. That gives the agent a clear when-to-use-this vs when-to-use-sibling signal.

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

All FedWatch — Federal Funding & Lien Watcher toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources