List open Alberta Purchasing Connection opportunities closing soon.
| Name | Required | Description | Default |
|---|---|---|---|
| days | No | Show opportunities closing within N days (default 30) | |
| limit | No | Maximum results (default 20, max 50) | |
| category | No | Optional category: services, goods, or construction |
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?
No annotations are present, so the description carries full burden for behavioral disclosure. It does not mention read-readiness, authorization, rate limits, or what 'closing soon' specifically means (e.g., relative to current date). Only the default parameter hints at a 30-day window.
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?
Single sentence, no fluff, essential information front-loaded. Every word contributes to understanding the tool's 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?
For a simple list tool with no output schema, the description is mostly complete. It identifies the source, region, and temporal filter. However, it could clarify that results are sorted by deadline or what fields are returned.
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 parameters are already well-documented. The description adds no additional meaning beyond the schema, staying at baseline for a fully annotated schema.
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 verb (list), resource (Alberta Purchasing Connection opportunities), and temporal scope (closing soon). The tool name further specifies 'alberta_deadlines', making it distinct from generic siblings like 'list_deadlines' or 'list_upcoming_deadlines'.
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?
No guidance provided on when to use this tool versus siblings such as 'find_alberta_opportunities' or 'list_upcoming_deadlines'. The description does not mention alternatives, prerequisites, or exclusion criteria.
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.
Many tools have overlapping purposes, e.g., multiple search/find tools (find_opportunities, find_matching_opportunities, search_opportunities, etc.) and detail retrieval tools (get_opportunity_details, get_alberta_opportunity_details, get_contract_details). This creates ambiguity for an agent to select the correct tool.
Most tools follow a verb_noun convention in snake_case (e.g., search_contracts, watch_opportunity). Some deviations like bid_no_bid_scorecard use a multi-word verb, but overall the pattern is consistent.
25 tools is on the higher side for this domain. While the number could be justified by the need to handle both federal and provincial opportunities, many tools are redundant, making the surface feel heavy.
Core workflows (search, get details, watch/unwatch, set/profile, analyze) are covered. Minor gaps exist, like no batch operations or tool to clear watchlist, but the surface is largely complete for contract tracking.
