Skip to main content
Glama

NetGrant — Canadian funding

by ca.netgrant

compare_opportunities

Fetch 2–4 opportunities at once so you can present them side by side. Use after search_opportunities when the user is choosing between a few options.

Returns the full detail rows (including eligibility + body) for every id, in the order requested. Present them as a comparison table — rows = attributes (funding, deadline, region, eligibility highlights), columns = the opportunities — then recommend which fits the user best and why.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesArray of 2–4 opportunity UUIDs (from search_opportunities) to compare.

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It states that it returns full detail rows including eligibility and body, in requested order. This is sufficient for a read-only fetch, though it could mention error handling or missing IDs.

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?

The description is concise with two main sentences and one output-related sentence. It is front-loaded with the core action. Some presentation advice could be separated, but overall efficient.

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 fully explains the return value (full detail rows, order) and provides context on when to use. It also advises on presentation and recommendation, making it complete for the agent.

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?

The parameter 'ids' is well-described in the schema (array of 2-4 UUIDs). The description does not add extra semantics beyond restating the output format, so baseline 3 is appropriate given 100% schema coverage.

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 tool's purpose: fetching 2-4 opportunities for side-by-side comparison. It uses a specific verb ('fetch') and resource ('opportunities'), and distinguishes itself from siblings by specifying it is used after search_opportunities when choosing between options.

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 says when to use: 'Use after search_opportunities when the user is choosing between a few options.' It also provides guidance on how to present results, making the usage context very clear.

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