Skip to main content
Glama

FundingLandscape

by io.github.tettertotter
OverviewDiscussionsAdmin

Deadline Calendar

deadline_calendar
Read-onlyIdempotent

Get upcoming funding deadlines for planning an application schedule. Default compact mode returns a merged results list of lean rows (id/title/org/deadline/daysUntil and direct url when it fits) plus section counts/index ranges so grants and procurement stay balanced without duplicating every row. Pass compact:false for full descriptions, quality details, and full sections.grants / sections.procurement arrays. Returns a bounded page of up to 50 candidate rows per section before calendar exclusions, not a complete calendar for the requested window. coverage preserves per-section candidate counts and executable candidate-search continuations; counts are not exact eligible totals. Non-biddable notices (Sources Sought, Award notices, etc.) and past/undated rows are excluded. Pass category to restrict to one type (e.g. "procurement" for contracts only). Available to authenticated free and paid accounts, within their search allowance. Free-plan listing-access limits still apply. Counts toward your monthly searches.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoAlternative to weeks: exact number of days ahead to show (default: 28, max: 365)
weeksNoNumber of weeks ahead to show (default: 4, max: 12)
compactNoReturn compact rows by default to keep agent payloads small. Long titles/orgs/links may be shortened or omitted; set false for full descriptions, nested quality details, and full section arrays.
categoryNoOptional. Restrict to ONE category instead of the default balanced grants+procurement view (e.g. "grant", "procurement", "prize"). Omit to get both grants and procurement as separate sections.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / compact
      Added value: +{
+  "default": true,
+  "description": "Return compact rows by default to keep agent payloads small. Long titles/orgs/links may be shortened or omitted; set false for full descriptions, nested quality details, and full section arrays.",
+  "type": "boolean"
+}
    • addedInput schema / properties / days
      Added value: +{
+  "description": "Alternative to weeks: exact number of days ahead to show (default: 28, max: 365)",
+  "type": "number"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / category / description
      Previous value: -"Filter to specific category (e.g., \"Grant\", \"Construction\")"New value: +"Optional. Restrict to ONE category instead of the default balanced grants+procurement view (e.g. \"grant\", \"procurement\", \"prize\"). Omit to get both grants and procurement as separate sections."
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only cover safety (readOnly/idempotent/non-destructive), and the description layers on substantial behavioral context: a bounded page of ~50 candidates per section, exclusion of non-biddable and past/undated rows, counts that are not exact eligible totals, authenticated free/paid requirement, and that the call counts toward a monthly search allowance.

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?

Purpose is front-loaded in the first sentence and subsequent sentences each carry a distinct constraint. It is dense and somewhat run-on in the middle (compact/coverage/counts), with mild restatement of the compact flag already in the schema, but little is truly wasted.

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?

There is no output schema and no annotations covering returns, so the description must carry that load and it does: it describes the results shape, section counts and index ranges, the coverage continuations, exclusion rules, and pagination bounds. An agent has enough to call and interpret it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description still adds value: it explains the compact-vs-full payload tradeoff in terms of merged `results` rows and section arrays, and clarifies that omitting `category` yields separate grants and procurement sections rather than a single type.

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+resource (get upcoming funding deadlines) and scopes it to planning an application schedule. It also distinguishes the default balanced grants+procurement view from the single-category mode. It does not name any sibling search tool to route the agent, so it stops short of full differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete guidance on when to pass compact:false and when to pass category, which is genuinely useful. However, with many lookalike siblings (search_grantsplus, search_procurement, batch_search_*), it never says when to prefer this calendar over a search tool. Usage is implied rather than contrasted.

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