Skip to main content
Glama

workspace-alberta

by io.github.HarleyCoops
OverviewDiscussionsAdmin

Process bid documents

process_bid_room

Process tender attachments in E2B: sends documents and business context to E2B, PDF page images/images and extracted evidence to Cohere Parse and Command A+. See /privacy for processing locations. For Alberta APC postings, the first call returns a private upload link: the user downloads the documents with their own APC supplier account and uploads them, then you call again with upload_token. Returns within 145 seconds including setup; large packages may time out. Retry with fewer attachments; a timeout is not a completed analysis. Hosted: sign-in and an active workspaceAlberta Pro subscription required.

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
upload_tokenNoFor APC only: the upload_token from an earlier process_bid_room result. APC releases documents only to the user's own signed-in supplier account, so the first call returns a private upload link; after the user uploads the files they downloaded from APC, call again with this token to process them.
max_attachmentsNoMaximum procurement files to process (default 5, max 5). Use 0 explicitly for a notice-only review; missing/gated documents do not count as complete coverage.
business_contextNoOptional company capabilities or bid context. If omitted, the saved business profile is used.
apc_document_urlsNoFor APC only: map document IDs from get_opportunity_details to already authorized, publicly accessible HTTPS copies. This tool never signs in to APC, registers supplier interest, subscribes notifications, or accepts authenticated download URLs. Copies are sent to E2B and their contents to Cohere.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / upload_token
      Added value: +{
+  "description": "For APC only: the upload_token from an earlier process_bid_room result. APC releases documents only to the user's own signed-in supplier account, so the first call returns a private upload link; after the user uploads the files they downloaded from APC, call again with this token to process them.",
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties / apc_document_urls
      Added value: +{
+  "additionalProperties": {
+    "format": "uri",
+    "type": "string"
+  },
+  "description": "For APC only: map document IDs from get_opportunity_details to already authorized, publicly accessible HTTPS copies. This tool never signs in to APC, registers supplier interest, subscribes notifications, or accepts authenticated download URLs. Copies are sent to E2B and their contents to Cohere.",
+  "maxProperties": 5,
+  "type": "object"
+}
    • changedInput schema / properties / max_attachments / description
      Previous value: -"Maximum direct attachments to process (default 5, max 5)"New value: +"Maximum procurement files to process (default 5, max 5). Use 0 explicitly for a notice-only review; missing/gated documents do not count as complete coverage."
  3. Changed5 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / command_timeout_seconds
      Removed value: -{
-  "default": 420,
-  "description": "Sandbox command timeout in seconds (default 420)",
-  "type": "integer"
-}
    • addedInput schema / properties / max_attachments / maximum
      Added value: +5
    • addedInput schema / properties / max_attachments / minimum
      Added value: +0
    • removedInput schema / properties / timeout_seconds
      Removed value: -{
-  "default": 900,
-  "description": "E2B sandbox timeout in seconds (default 900)",
-  "type": "integer"
-}
  4. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false) by disclosing data flows and destinations (E2B, Cohere Parse/Command A+, /privacy), a hard 145-second latency bound, timeout semantics, retry behavior, and hosted auth/subscription prerequisites. This is exactly the behavioral context annotations cannot carry.

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?

Front-loads the core pipeline, then layers privacy, APC flow, timeout and auth in a logical order with every sentence carrying operational weight. It is dense and repeats the upload_token APC flow already stated in the schema, costing a little efficiency.

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?

For a 6-parameter, nested-object, no-output-schema tool, it covers the two-step APC return (upload link), timeout budget, retry policy and auth requirements thoroughly. It does not describe what a successful analysis returns, which matters given there is no output schema to fall back on.

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% and the schema already documents profile, reference, upload_token, max_attachments, business_context and apc_document_urls in detail, so the baseline is 3. The description largely restates the APC upload_token flow already present in the parameter description and adds no new syntax or constraints.

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?

States a specific verb and resource and details the pipeline ('sends documents and business context to E2B, PDF page images... to Cohere Parse and Command A+'), so the agent knows this is the deep document-processing tool rather than a lookup. It never names a sibling (e.g. analyze_contract_with_cohere) to sharpen the boundary, so differentiation is inferential rather than explicit.

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

Usage Guidelines4/5

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

Gives explicit conditional flows: the two-step APC path (first call returns a private upload link, call again with upload_token), retry guidance ('Retry with fewer attachments'), and the timeout caveat ('a timeout is not a completed analysis'). It stops short of saying when to prefer a different sibling tool, so it is clear context without explicit alternatives.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources