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). Paid feature. 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.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description layers on material behavior: a hard cap of ~50 candidate rows per section, exclusion of non-biddable notices and past/undated rows, coverage counts that are not exact eligible totals, and that it is a paid feature counting toward monthly searches. None of this is present in the structured fields.

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 and most sentences carry distinct information (mode behavior, row cap, exclusions, coverage semantics, cost). It is dense and slightly long, with the merged-results sentence doing a lot of work, but nothing is clearly 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, so the description must describe returns, and it does: results list shape, section counts/index ranges, sections.grants/sections.procurement, and coverage continuations. Combined with the exclusions and bounded-page caveats, an agent has everything needed 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, but the description adds real meaning beyond the schema by explaining what compact toggles (merged lean rows with section counts/index ranges vs full descriptions and full sections.grants/sections.procurement arrays) and what category does (default is a balanced grants+procurement view; "procurement" restricts to contracts only).

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 ("Get upcoming funding deadlines") plus the intent ("for planning an application schedule"), and its deadline-calendar framing clearly sets it apart from the sibling search_* tools. An agent can tell what it returns (merged deadline rows with daysUntil and section counts) without opening 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 Guidelines4/5

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

Gives concrete usage conditions for its modes (compact default vs compact:false, pass category to restrict to one type) and warns that it returns a bounded page rather than a complete calendar, which steers correct expectations. It does not, however, explicitly name which sibling search tool to use instead for exhaustive discovery, so the alternative-selection guidance is implicit.

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