grant-api-30-day-passActivate 30 days of bearer-token access to every Genuine Good Grants API tool, subject to a 1,000-request fair-use limit. The client supplies its own random token; Genuine Good stores only its SHA-256 hash. Paid HTTP endpoint: https://genuinegood.online/v1/grants/pass. Price: $15.00 USDC via x402 on Base.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses material behavior beyond the annotations: the 1,000-request fair-use limit, client-supplied token with only its SHA-256 hash stored, paid endpoint, and price. These details are highly relevant for an agent deciding whether to invoke a paid activation tool and what side effects to expect.
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?
Four tight sentences convey the action, constraints, security model, endpoint, and price, with the primary verb and resource front-loaded. Every sentence earns its place.
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?
The description covers purpose, rate limit, token handling, endpoint, and pricing, and points to an OpenAPI contract for endpoint-specific schema details. It does not describe the success or error response shape, but for a zero-parameter activation tool with a linked contract this is a minor gap.
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?
The tool has zero parameters and 100% schema description coverage, so there are no parameter semantics for the description to expand. The description still adds relevant invocation context by mentioning that the client supplies its own random token.
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 states a specific action and target: 'Activate 30 days of bearer-token access to every Genuine Good Grants API tool.' It is clearly differentiated from the sibling federal-grant tools, which perform search/detail operations rather than access activation.
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 paid endpoint, activation behavior, and fair-use limit make it clear that this tool is for obtaining API access before using the grant tools. However, it never explicitly states when not to use it or names alternatives, so the routing guidance is clear but not fully explicit.
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.
Most tools map cleanly to distinct stages: search, detail, preflight, and access pass are clearly separated. The only real tension is between grant-eligibility-fit and grant-opportunity-brief, since both match current opportunities and surface eligibility/deadline signals; the descriptions distinguish ranking/reasons from narrative briefs, but an agent could still pick the wrong one.
Names are consistently lowercase hyphenated noun phrases, but the prefix pattern splits between federal-grant-* and grant-*, and grant-api-30-day-pass mixes in API and a duration. This is readable but not a single predictable verb_noun convention, so it feels slightly inconsistent.
Six tools is a well-scoped count for a grants discovery/analysis service: raw search and detail, screening, ranking, briefing, and an access-pass tool. Each tool fills a distinct role in the workflow without the surface feeling bloated or thin.
The server covers the core pipeline from discovering opportunities, retrieving official records, evaluating fit, and producing briefs. It lacks conveniences like saved shortlists or batch comparison, but agents can assemble those from search/detail outputs, so the gaps are minor.