Skip to main content
Glama

workspace-alberta

by io.github.HarleyCoops

process_bid_room

Use an E2B sandbox to process tender attachments and call Cohere Command A+ inside the sandbox for bid-room analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
referenceYesCanadaBuys or Alberta APC reference number
max_attachmentsNoMaximum direct attachments to process (default 5, max 5)
timeout_secondsNoE2B sandbox timeout in seconds (default 900)
business_contextNoOptional company capabilities or bid context. If omitted, the saved business profile is used.
command_timeout_secondsNoSandbox command timeout in seconds (default 420)

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided, so description must cover behavioral traits. It discloses use of E2B sandbox and Cohere Command A+, but does not mention side effects (e.g., sandbox destruction), authentication needs, rate limits, or whether operations are read-only. The timeout parameters provide some transparency on execution duration.

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?

Single sentence (25 words) is concise and front-loaded with the main action. However, for a tool with 6 parameters and nested objects, a slightly more structured description (e.g., brief bullets) could improve readability.

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?

Covers core action but lacks explanation of return values (no output schema), error conditions, prerequisites (e.g., reference format), and sandbox lifecycle. Adequate for basic understanding but incomplete for fully autonomous agent use.

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%, and description adds value by explaining that 'profile' is an inline override, 'business_context' overrides saved profile, and 'max_attachments' has a hard limit of 5. Context like 'On the shared public endpoint...' provides usage nuance beyond the schema.

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?

Description clearly states the verb (process), the resource (tender attachments), and the context (E2B sandbox, Cohere Command A+). Differentiates from sibling tools like analyze_contract_with_cohere by emphasizing sandbox execution and attachment processing.

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?

No explicit guidance on when to use this tool vs siblings (e.g., analyze_contract_with_cohere, bid_no_bid_scorecard). Usage is implied by the unique sandbox+attachment processing, but no exclusions or prerequisites are mentioned.

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