continental_grant_statusStatus of your own grant application: open, granted (with the ledger seq and Markers) or declined (with the reasoning).
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | No | Your key, when this client cannot send it as an Authorization header (e.g. a chat connector). Same rights as the header; the header wins if both are present. | |
| application_id | Yes | From continental_grant_apply |
Changes observed during successful MCP inspections.
Input schema / properties / api_keyAdded value: +{
+ "description": "Your key, when this client cannot send it as an Authorization header (e.g. a chat connector). Same rights as the header; the header wins if both are present.",
+ "pattern": "^tc_(live|visit)_[a-f0-9]{64}$",
+ "type": "string"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish that this is read-only, idempotent, and non-destructive. The description adds meaningful behavioral detail by enumerating the possible outcomes: open, granted (with ledger seq and Markers), or declined (with reasoning). This is especially valuable because there is no output schema.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single efficient sentence with no filler. It front-loads the scope ('your own grant application') and then lists the relevant outcome states with their key details. Every part serves a purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of an output schema, the description does a good job of explaining what result variants to expect. It covers open, granted, and declined states and mentions the accompanying data. It does not explain error cases or the exact structure for an 'open' result, but for a simple read-only status check this is reasonably complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The description itself does not add much parameter-level detail beyond what the schema already provides. The schema already explains application_id is a UUID from continental_grant_apply and api_key is an alternative to the Authorization header.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the resource (your own grant application) and the operation's purpose (reporting status). It also distinguishes the scope by saying 'your own', which differentiates it from checking others' applications. It lacks an explicit verb like 'retrieves' or 'gets', but the meaning is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies that this tool is for checking the status of a grant application after applying, but it does not explicitly state when to use it versus alternatives. There is no direct mention of sibling tools or exclusionary guidance. The schema's application_id note referencing continental_grant_apply provides some context, but the description itself gives only implied usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.