Skip to main content
Glama

Ca Grants

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Ca Grants By Agency

ca_grants_by_agency
Read-onlyIdempotent

List the grant opportunities administered by a given California state department, agency, commission, or conservancy, matching the agency name as a forgiving case-insensitive substring so partial names like "Water Resources" or "Recycling" work. Returns the matched official agency names, a count breakdown by status, and the grant records with title, categories, eligible applicants, estimated funding, and deadline. Answers "what grants does CalRecycle offer", "grant programs from the California Energy Commission", "Department of Parks and Recreation funding opportunities".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax records to return (default 25, max 100).
agencyYesCalifornia state department / agency name or fragment, case-insensitive, e.g. "Recycling", "Energy Commission", "Parks and Recreation", "Fish and Wildlife".
offsetNoNumber of matching records to skip, for pagination (default 0).
statusNoWhich opportunities to include (default "all"; use "active" for only what is open now).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "agency": "Recycling",
-    "limit": 3,
-    "status": "active"
-  }
-]New value: +[
+  {
+    "agency": "Fish and Wildlife",
+    "limit": 10,
+    "status": "active"
+  }
+]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, non-destructive. The description adds behavioral details: case-insensitive substring matching, return structure (matched names, count breakdown, grant fields). 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is 3-4 sentences, front-loaded with purpose, then details and examples. Every sentence adds value with no wasted words.

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 adequately explains what is returned (matched names, count breakdown, grant records with fields). Covers input and output sufficiently for an agent to understand the tool.

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 100%, so baseline is 3. The description reinforces the forgiving substring matching and provides examples, but does not add significant new meaning beyond what's in the schema parameter descriptions.

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?

Clearly states it lists grant opportunities by agency, with specific verb and resource. The description explicitly mentions matching agency name as substring and provides example queries, distinguishing it from sibling tools like ca_search_grants or ca_get_grant.

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 clear context for when to use via example questions ('what grants does CalRecycle offer'). Does not explicitly state when not to use or mention alternatives, but the examples and sibling list imply its specific niche.

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