Skip to main content
Glama

Ca Grants

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Ca Grants Closing Soon

ca_grants_closing_soon
Read-onlyIdempotent

List currently-open State of California grant opportunities whose application deadline falls within the next N days, soonest deadline first, so an applicant can see what is about to expire. Returns each grant with its days remaining, deadline timestamp, administering California state department, eligible applicant types, estimated funding available, and official link. Also reports separately how many active grants accept applications on a rolling "Ongoing" basis with no fixed due date, and how many rows carried an unreadable deadline. Answers "which California state grants close this month", "urgent CA grant deadlines", "what should I apply for before it closes".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoDeadline window in days from today (default 30, max 365).
limitNoMax records to return (default 25, max 100).
categoryNoOptional: restrict to one grant category, case-insensitive, e.g. "Environment & Water".
applicant_typeNoOptional: restrict to one eligible-applicant type, case-insensitive, e.g. "Nonprofit", "Tribal Government".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "days": 30,
-    "limit": 3
-  }
-]New value: +[
+  {
+    "days": 60,
+    "limit": 10
+  }
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations confirm readOnlyHint, idempotentHint, destructiveHint=false. The description adds behavioral details: sorting by deadline, reporting separate counts for rolling and unreadable deadlines, and the specific fields returned. No contradictions.

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?

The description is front-loaded with the main purpose, followed by returned fields and example queries. It is slightly verbose but each sentence adds value. Could be more concise without losing clarity.

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?

Given no output schema, the description fully explains the return information (days remaining, deadline, department, applicant types, funding, link, plus counts for rolling and unreadable). Parameters are documented, annotations are safe, and the use case is clear. No gaps.

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%, and parameter descriptions already include defaults and max values. The tool description does not add new parameter information but frames parameters in the context of grant deadlines. Baseline 3 is appropriate.

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 clearly states the tool lists currently-open CA grant opportunities closing within N days, sorted by soonest deadline, and specifies the returned fields. It distinguishes from siblings like ca_grants_by_agency and ca_search_grants by its focus on urgent deadlines and inclusion of rolling grants and unreadable row counts.

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?

Usage is well-defined with explicit example queries like 'which California state grants close this month' and 'urgent CA grant deadlines'. It does not explicitly state when not to use, but the context and sibling tools provide implicit alternatives. The description could improve by mentioning when to use ca_search_grants instead.

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

All Ca Grants 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