Skip to main content
Glama

FundingLandscape

by io.github.tettertotter
OverviewDiscussionsAdmin

Batch Search Grants

batch_search_grantsplus
Read-onlyIdempotent

DEPRECATED ALIAS — prefer search_grantsplus with a queries[] array, which now runs the identical batch fan-out. Kept for backward compatibility; behavior is unchanged. Search grants, prizes, and foundations comprehensively. Returns 10 results by default (~4KB). Use detail_level and max_results to control response size. Response includes total available count so you can request more if needed. Counts toward your monthly searches. A batch counts as 1 call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sinceNoStateless alternative to posted_within_days/new_within_days: ISO 8601 instant. Only opportunities ingested at/after this instant.
offsetNoNumber of results to skip for pagination (default: 0). Use with max_results to page through large result sets. Example: offset=100 with max_results=100 returns results 101-200.
sourceNoFilter every batch sub-query to a specific source/domain, e.g. "grants.gov" or "deq.nc.gov".
queriesYesArray of 2-5 search queries to run in parallel. Example for clean energy: ["renewable energy grants", "solar wind funding", "clean energy nonprofit", "sustainability grants", "green technology funding"]
max_resultsNoMaximum opportunities to return (default: 10, max: 100). Token cost guide: 10 results ~4KB, 25 results ~10KB, 50 results ~20KB, 100 results ~40KB.
detail_levelNoControls response verbosity. minimal (~120 bytes/result): id, title, org, deadline, url, qualityScore - best for scanning 50+ results. compact (~400 bytes/result, DEFAULT): adds snippet, category, status, deadlineType, daysUntilDeadline, deadlineLabel, and lastRoundClosedAt - good for recommendations. full (~1.5KB/result): everything including eligibility, amounts - only use with max_results <= 10.compact
user_contextNo
grants_filtersNoGrants.gov specific filters
new_within_daysNoBackwards-compatible alias for posted_within_days. Only opportunities ingested (added by us) in the last N days -- for recurring/delta checks ("what is new since my last check"). Applied per sub-query before dedupe; response includes deduped newSince.newCount and the newest/oldest ingest timestamp in the window.
posted_within_daysNoPreferred alias for new_within_days: only opportunities ingested (added by us) in the last N days. Applied per sub-query before dedupe; the response includes a deduped newSince summary. If both posted_within_days and new_within_days are supplied, posted_within_days wins.
include_foundationsNoAlso search private foundations (default: true)
max_response_tokensNoToken budget for response (default: 4000 ≈ 16KB). Server auto-caps results to fit. Increase to 8000-16000 for more results per call, decrease to 2000 for lightweight scanning.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / detail_level / description
      Previous value: -"Controls response verbosity. minimal (~120 bytes/result): id, title, org, deadline, url, qualityScore - best for scanning 50+ results. compact (~300 bytes/result, DEFAULT): adds snippet, category, status - good for recommendations. full (~1.5KB/result): everything including eligibility, amounts - only use with max_results <= 10."New value: +"Controls response verbosity. minimal (~120 bytes/result): id, title, org, deadline, url, qualityScore - best for scanning 50+ results. compact (~400 bytes/result, DEFAULT): adds snippet, category, status, deadlineType, daysUntilDeadline, deadlineLabel, and lastRoundClosedAt - good for recommendations. full (~1.5KB/result): everything including eligibility, amounts - only use with max_results <= 10."
  2. Changed1 schema field changed
    • changedInput schema / properties / max_results / description
      Previous value: -"Maximum results to return (default: 10). Token cost guide: 10 results ~4KB, 25 results ~10KB, 50 results ~20KB, 100 results ~40KB. No hard cap - use judgment based on your context window."New value: +"Maximum opportunities to return (default: 10, max: 100). Token cost guide: 10 results ~4KB, 25 results ~10KB, 50 results ~20KB, 100 results ~40KB."
  3. Changed1 schema field changed
    • addedInput schema / properties / source
      Added value: +{
+  "description": "Filter every batch sub-query to a specific source/domain, e.g. \"grants.gov\" or \"deq.nc.gov\".",
+  "type": "string"
+}
  4. Changed3 schema fields changed
    • changedInput schema / properties / new_within_days / description
      Previous value: -"Only opportunities ingested (added by us) in the last N days -- for recurring/delta checks (\"what is new since my last check\"). Applied per sub-query before dedupe; the final merged/deduped list is sorted newest-ingested-first when this is set. Response includes newSince.newCount and the newest/oldest ingest timestamp in the window."New value: +"Backwards-compatible alias for posted_within_days. Only opportunities ingested (added by us) in the last N days -- for recurring/delta checks (\"what is new since my last check\"). Applied per sub-query before dedupe; response includes deduped newSince.newCount and the newest/oldest ingest timestamp in the window."
    • addedInput schema / properties / posted_within_days
      Added value: +{
+  "description": "Preferred alias for new_within_days: only opportunities ingested (added by us) in the last N days. Applied per sub-query before dedupe; the response includes a deduped newSince summary. If both posted_within_days and new_within_days are supplied, posted_within_days wins.",
+  "type": "number"
+}
    • changedInput schema / properties / since / description
      Previous value: -"Stateless alternative to new_within_days: ISO 8601 instant. Only opportunities ingested at/after this instant."New value: +"Stateless alternative to posted_within_days/new_within_days: ISO 8601 instant. Only opportunities ingested at/after this instant."
  5. Changed2 schema fields changed
    • addedInput schema / properties / new_within_days
      Added value: +{
+  "description": "Only opportunities ingested (added by us) in the last N days -- for recurring/delta checks (\"what is new since my last check\"). Applied per sub-query before dedupe; the final merged/deduped list is sorted newest-ingested-first when this is set. Response includes newSince.newCount and the newest/oldest ingest timestamp in the window.",
+  "type": "number"
+}
    • addedInput schema / properties / since
      Added value: +{
+  "description": "Stateless alternative to new_within_days: ISO 8601 instant. Only opportunities ingested at/after this instant.",
+  "type": "string"
+}
  6. Changed1 schema field changed
    • addedInput schema / properties / user_context / properties / organization_type / description
      Added value: +"Common natural-language phrasing (e.g. \"501(c)(3) nonprofit\") is also parsed; unparseable values are ignored with an explicit note in the response."
  7. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, and the description's 'Search' verb is consistent with them. The description adds genuinely useful behavioral context beyond annotations: quota accounting ('Counts toward your monthly searches. A batch counts as 1 call'), response size behavior (~4KB for 10 results), and the guarantee that behavior is unchanged from the deprecation. Minor omissions like rate limits or error behavior prevent a 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?

Five short sentences, each earning its place: deprecation routing first, then purpose, default size, control knobs, pagination hint, and billing implication. No fluff or repeated schema content. Front-loading the deprecation warning is exactly what an agent needs before deciding whether to call this tool.

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?

For a 12-parameter tool with nested objects and no output schema, the description covers the essential operational facts: purpose, default response size, size control, total-count pagination signal, deprecation status, and quota cost. The return-value picture is partially left to the schema (e.g. newSince summaries), but the description fills the most critical gaps an agent faces. Not exhaustive enough for a 5given no output schema and 12 parameters.

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 92%, so the schema already documents nearly all parameters in detail. The description adds a small amount of cross-parameter guidance—that detail_level and max_results jointly control response size, and the ~4KB default scaling—but does not substantially go beyond the schema's already rich parameter descriptions. Baseline 3 is appropriate given the high schema coverage.

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 states a specific verb and resource ('Search grants, prizes, and foundations comprehensively') and immediately establishes its role as a deprecated alias of search_grantsplus, distinguishing it from the preferred sibling. An agent can tell exactly what it does and how it relates to its siblings without inspecting the schema.

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?

The first sentence explicitly routes agents to the preferred alternative ('prefer search_grantsplus with a queries[] array, which now runs the identical batch fan-out') and states this tool exists only for backward compatibility. It also gives concrete control guidance: 'Use detail_level and max_results to control response size' and explains the pagination cue ('Response includes total available count so you can request more if needed').

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

All FundingLandscape 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