Skip to main content
Glama

Ca Grants

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Ca Get Grant

ca_get_grant
Read-onlyIdempotent

Fetch the complete detail record for one California state grant opportunity by its California Grants Portal ID (PortalID). Returns the full narrative purpose and description, eligible applicant types and eligibility notes, geography served, funding source, whether matching funds are required, estimated funds available and per-award amounts, funding method (reimbursement vs advance), the open date and application deadline, whether electronic submission is accepted, agency contact information, and links to the official grant page and agency site. Use after ca_search_grants to read the full terms of a specific California state grant.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
portal_idYesThe California Grants Portal ID from a search result, e.g. "189801".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "portal_id": "189801"
-  }
-]New value: +[
+  {
+    "portal_id": "171843"
+  }
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds specific behavioral context by enumerating the data returned (e.g., narrative purpose, eligible applicant types, funding details). No contradictions with annotations.

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?

The description is concise (three sentences) and well-structured: main action first, then return details, then usage guidance. Every sentence adds value with no redundancy.

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 thoroughly lists the fields returned (narrative, eligibility, geography, funding, dates, etc.), making it complete for agent understanding.

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%, with the parameter already described as 'The California Grants Portal ID from a search result, e.g. "189801".' The description reiterates this but adds no significant new meaning beyond the schema.

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 verb 'Fetch', the resource 'complete detail record for one California state grant opportunity', and the identifier 'California Grants Portal ID (PortalID)'. It distinguishes from sibling tools by mentioning 'Use after ca_search_grants'.

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

Usage Guidelines5/5

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

The description explicitly provides usage context: 'Use after ca_search_grants to read the full terms of a specific California state grant.' This tells the agent when and in what sequence to use this tool.

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