Skip to main content
Glama

workspace-alberta

by io.github.HarleyCoops

find_opportunities

Find government contracts that match your business profile. Returns scored and ranked opportunities with explanations of why each one fits your capabilities. Pass an inline profile to describe the business per call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoOnly show contracts closing within N days (default: 60)
limitNoMaximum opportunities to return (default: 15)
profileNoInline business profile used for this call only. Overrides any saved profile. On the shared public endpoint without a subscriber key, this is the way to describe your business.

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It discloses the return type (scored/ranked with explanations) but does not mention side effects, auth requirements, rate limits, or data freshness. The description is adequate but not comprehensive.

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

Conciseness5/5

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

The description is two sentences: the first front-loads the core purpose; the second adds the key detail about inline profile. No wasted words.

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

Completeness3/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 partially describes return (scored/ranked with explanations) but lacks details on error cases, data freshness, or behavior when no matches exist. The tool has moderate complexity with a nested object, so it is adequate but not fully complete.

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?

Schema coverage is 100%, providing default behavior for days and limit, and full structure for profile. The description adds only a high-level note about inline profile, which does not significantly add beyond the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool finds government contracts matching a business profile and returns scored/ranked opportunities with explanations. It is specific with verb and resource, but does not explicitly differentiate from siblings like find_matching_opportunities or find_alberta_opportunities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by mentioning inline profile and per-call nature, but provides no explicit when-to-use or when-not-to-use guidance nor mentions alternatives among sibling tools.

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

All workspace-alberta 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

B3.1/5.0
Disambiguation2/5

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.

Naming Consistency4/5

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.

Tool Count3/5

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.

Completeness4/5

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.

Resources