Skip to main content
Glama

workspace-alberta

by io.github.HarleyCoops
OverviewDiscussionsAdmin

List procurement deadlines

list_deadlines
Read-only

List CanadaBuys and Alberta APC opportunities closing soon.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoShow opportunities closing within N days (default 30)
limitNoMaximum combined results (default 20, max 50)
sourceNoall, federal, or albertaall
categoryNoOptional category filter
provinceNoOptional province or delivery region filter

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNo
countNo
warningsNo
opportunitiesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / opportunities / items / properties / closes_at
      Added value: +{
+  "description": "Closing time as ISO 8601 in Alberta time with UTC offset; empty when unknown",
+  "type": "string"
+}
    • addedOutput schema / properties / opportunities / items / properties / closing / description
      Added value: +"Closing value exactly as the source published it"
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "type": "integer"
+    },
+    "kind": {
+      "type": "string"
+    },
+    "opportunities": {
+      "items": {
+        "properties": {
+          "buyer": {
+            "type": "string"
+          },
+          "category": {
+            "type": "string"
+          },
+          "closing": {
+            "type": "string"
+          },
+          "reference": {
+            "type": "string"
+          },
+          "region": {
+            "type": "string"
+          },
+          "solicitation": {
+            "type": "string"
+          },
+          "source": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "warnings": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety and open-world profile is covered. The description adds only the source scope (CanadaBuys + Alberta APC), and says nothing about ordering, pagination, or what 'closing soon' resolves to beyond the schema default of 30 days.

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?

A single tight sentence with the source scope front-loaded and zero waste. It is efficient, though the brevity comes at the cost of the disambiguation the tool actually needs.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values need not be explained, but the description leaves the critical ambiguity unresolved: which of the three deadline-listing siblings to call. For a zero-required-parameter tool easily confused with its neighbors, that omission is significant.

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 description coverage is 100% and all five parameters carry defaults, enums-by-name, and constraints (e.g. max 50) in the schema itself. The description adds no syntax, unit, or format meaning beyond what the schema already provides, so 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?

Specific verb ('List') plus resource ('opportunities closing soon') and names the two source domains CanadaBuys and Alberta APC, so an agent knows what it retrieves. However it does nothing to distinguish itself from the near-identical siblings list_upcoming_deadlines and list_alberta_deadlines, which is the main risk for this tool.

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

Usage Guidelines2/5

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

No when-to-use statement, no prerequisites, and no mention of alternatives. With three name-adjacent siblings (list_deadlines, list_upcoming_deadlines, list_alberta_deadlines) all covering deadlines, the agent is left to guess which one applies.

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