Skip to main content
Glama

Show federal grant details

show_grant_details
Read-onlyIdempotent

Reads up to 20 federal opportunity numbers or numeric IDs from Grants.gov and returns details, per-item errors, and XLSX and ICS downloads for a pasted shortlist. Covers grant details and closing dates only; it does not write, submit or track grant applications.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "opportunities": "<opportunities>"
    },
    "name": "show_grant_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
opportunitiesYesOpportunity numbers or numeric IDs, e.g. ["2026-NTIA-TBCP", "359145"].

Output Schema

NameRequiredDescriptionDefault
pageYes
rowsYes
shownYes
errorsYes
sourceYes
matchedYes
summaryYes
has_nextYes
downloadsYes
attributionYes
retrieved_atYes
calendar_eventsYes
total_availableYes
deadline_time_noteYes
download_expires_atYes
deadline_time_includedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedOutput schema / properties / attribution
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / deadline_time_included
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / deadline_time_note
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / download_expires_at
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / retrieved_at
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / rows / items / properties / close_estimated
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / rows / items / properties / is_estimated
      Added value: +{
      +  "type": "boolean"
      +}
    • changedOutput schema / properties / rows / items / required
      Previous value: -[
      -  "number",
      -  "title",
      -  "agency",
      -  "status",
      -  "posted",
      -  "close",
      -  "days_left",
      -  "ceiling",
      -  "floor",
      -  "link"
      -]New value: +[
      +  "number",
      +  "title",
      +  "agency",
      +  "status",
      +  "posted",
      +  "close",
      +  "close_estimated",
      +  "is_estimated",
      +  "days_left",
      +  "ceiling",
      +  "floor",
      +  "link"
      +]
    • changedOutput schema / required
      Previous value: -[
      -  "summary",
      -  "source",
      -  "matched",
      -  "shown",
      -  "total_available",
      -  "page",
      -  "has_next",
      -  "rows",
      -  "errors",
      -  "downloads",
      -  "calendar_events"
      -]New value: +[
      +  "summary",
      +  "source",
      +  "retrieved_at",
      +  "matched",
      +  "shown",
      +  "total_available",
      +  "page",
      +  "has_next",
      +  "rows",
      +  "errors",
      +  "downloads",
      +  "download_expires_at",
      +  "calendar_events",
      +  "attribution",
      +  "deadline_time_included",
      +  "deadline_time_note"
      +]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), and the description adds genuinely new behavior: a hard 20-item batch ceiling, per-item error reporting rather than all-or-nothing failure, and downloadable XLSX/ICS artifacts. It doesn't say what happens to the other items when some fail or whether external Grants.gov availability affects results, which keeps it below 5.

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 sentences, no filler, with the batch scope and source front-loaded and the scope limitation trailing. Every clause carries information an agent needs.

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 one-parameter read tool with full annotations and an output schema, this covers source, limits, return shape family, and partial-failure semantics. Nothing needed to call it 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%, so the single 'opportunities' array with its min/max length and example is already fully documented. The description echoes the 'up to 20' and accepted format, adding marginal value but nothing beyond the schema.

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?

States a specific verb (reads) and resource (federal opportunity numbers/IDs from Grants.gov) plus the batch cap of 20, so the agent knows exactly what the tool retrieves. It implicitly separates itself from find_grant_opportunities by framing input as a 'pasted shortlist' of known IDs rather than a search, but never names the sibling outright.

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?

Clear context: use it when you already hold opportunity numbers or numeric IDs, and an explicit negative scope ('does not write, submit or track grant applications'). It stops short of the most useful routing instruction — that find_grant_opportunities should be used first to discover IDs when you don't have them.

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