Skip to main content
Glama

NetGrant — Canadian funding

by ca.netgrant

get_opportunity_details

Fetch full details for a single opportunity by ID. Use this after search_opportunities when:

  • The user wants to know more about a specific match

  • You need the full eligibility text to confirm a strong-match claim

  • The user wants to draft an application — you need the requirements

The response includes all fields including the full body text and eligibility criteria. Present the eligibility as a checklist when relevant.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesOpportunity UUID returned from search_opportunities

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description discloses that the response includes all fields including full body text and eligibility criteria. It suggests presenting eligibility as a checklist. Lacks explicit statement about read-only/idempotent nature, but context is strong.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

Description is brief and front-loaded with main purpose. Could slightly trim 'when relevant' but overall well-structured and no wasted sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given one parameter, full schema coverage, and no output schema, the description adequately explains response content (full body, eligibility) and presentation hint. Fairly complete for a simple retrieval tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with one parameter. Description adds value by noting the id comes from search_opportunities, which is helpful context beyond the schema description.

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 states 'Fetch full details for a single opportunity by ID' with a specific verb and resource. It distinguishes from siblings by focusing on a single opportunity after search_opportunities.

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?

Explicitly lists three scenarios when to use this tool (after search_opportunities for more details, to confirm eligibility claims, or to draft applications). This provides clear context and implies when not to use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All NetGrant — Canadian funding toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: searching, fetching details, comparing, checking eligibility, and subscribing. No overlap in functionality, and the descriptions guide the agent on when to use each.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (e.g., search_opportunities, get_opportunity_details), making them predictable and easy to understand.

Tool Count5/5

With 5 tools, the surface is well-scoped for the domain of Canadian funding. Each tool addresses a distinct user need without unnecessary overhead.

Completeness4/5

The tools cover the core workflow: search, view details, compare, check eligibility, and subscribe to alerts. Missing minor operations like editing a subscription, but overall the surface is complete for the stated purpose.

Resources