Skip to main content
Glama

Ca Grants

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Ca Search Grants

ca_search_grants
Read-onlyIdempotent

Search open State of California grant funding opportunities from the official California Grants Portal (grants.ca.gov) on data.ca.gov. Free-text search across grant titles, purposes and descriptions, with optional filters for status, category, and eligible applicant type. Each result returns the grant title, the administering California state department or agency, its categories, who is eligible to apply, estimated funding available, the application deadline, and a link to the official grant page. Defaults to currently-open (active) opportunities. Answers questions like "what California state grants can a nonprofit apply for right now", "state climate resilience funding in California", or "CalRecycle grant opportunities for tribal governments". This is CALIFORNIA STATE grant data, refreshed daily.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax records to return (default 20, max 100).
queryNoFree-text search across every field (title, purpose, description, agency), e.g. "climate", "wildfire resilience", "youth literacy".
offsetNoNumber of matching records to skip, for pagination (default 0).
statusNoWhich opportunities to include: "active" = currently open for applications (default), "forecasted" = announced but not yet open, "closed" = past deadline, "all" = every status.
categoryNoMatch one grant category, case-insensitive, against the semicolon-joined Categories list, e.g. "Environment & Water", "Housing", "Education". Call ca_list_grant_categories to see the values present in the data.
applicant_typeNoMatch one eligible-applicant type, case-insensitive, against the semicolon-joined ApplicantType list. Known values: "Nonprofit", "Public Agency", "Tribal Government", "Business", "Individual", "Other Legal Entity".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "applicant_type": "Nonprofit",
-    "limit": 3,
-    "query": "climate"
-  }
-]New value: +[
+  {
+    "limit": 10,
+    "query": "wildfire resilience",
+    "status": "active"
+  },
+  {
+    "applicant_type": "Tribal Government",
+    "category": "Environment & Water",
+    "limit": 10,
+    "status": "active"
+  }
+]
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations (readOnlyHint, openWorldHint, idempotentHint, destructiveHint) are consistent. The description adds context: daily data refresh, official source, and default filtering behavior, exceeding the annotations' information.

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?

Concise 6-sentence description, front-loaded with purpose, then details, then examples. No unnecessary words, all sentences earn their place.

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?

No output schema exists, but the description explicitly lists all returned fields (title, agency, categories, eligibility, funding, deadline, link). Also covers data refresh, default status, and source attribution, making the tool fully self-explanatory.

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% with detailed descriptions for all 6 parameters. The description adds some context (e.g., query searches across title/purpose/description/agency) but does not significantly extend beyond the schema. 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 it searches open CA grant opportunities with free-text and filters, and distinguishes from siblings like ca_get_grant and ca_grants_by_agency. The verb 'search' and resource 'California grant funding opportunities' are explicit.

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?

Provides example questions that the tool answers, implying when to use it. However, it does not explicitly state when not to use or mention alternatives, though context from sibling tools is present.

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