Skip to main content
Glama

workspace-alberta

by io.github.HarleyCoops
OverviewDiscussionsAdmin

Match procurement opportunities to my business

find_matching_opportunities
Read-only

Rank CanadaBuys and Alberta APC opportunities against a business profile. Pass an inline profile to describe the business per call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoOnly show opportunities closing within N days (default 60)
limitNoMaximum opportunities to return (default 15, max 30)
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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNo
countNo
matchesNo
warningsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "type": "integer"
+    },
+    "kind": {
+      "type": "string"
+    },
+    "matches": {
+      "items": {
+        "properties": {
+          "buyer": {
+            "type": "string"
+          },
+          "category": {
+            "type": "string"
+          },
+          "closing": {
+            "type": "string"
+          },
+          "days_until": {
+            "type": [
+              "integer",
+              "null"
+            ]
+          },
+          "reasons": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "reference": {
+            "type": "string"
+          },
+          "region": {
+            "type": "string"
+          },
+          "score": {
+            "type": "integer"
+          },
+          "solicitation": {
+            "type": "string"
+          },
+          "source": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "warnings": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds that the profile is 'inline' and 'per call only', and notes the public endpoint behavior without a subscriber key. This adds useful context beyond the annotations.

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?

Two sentences with zero waste. The main action is front-loaded, and the critical usage note about the inline profile is included in the second sentence.

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?

The tool has an output schema, so return values are covered. The description explains the core matching behavior and the profile mechanism. It could be more explicit about ranking criteria or how the profile is used, but the schema and annotations cover most operational needs.

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%, so the schema already documents all parameters thoroughly. The description adds the key context that the profile is 'inline' and 'per call only', which is valuable, but doesn't add much beyond what the schema already states.

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?

The description clearly states a specific verb ('Rank') and resource ('CanadaBuys and Alberta APC opportunities') against a business profile. It distinguishes itself from sibling tools like find_opportunities and find_alberta_opportunities by focusing on ranking/matching against a profile rather than simple searching or listing.

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?

The description implies the tool is for matching opportunities to a business profile, and the profile parameter description clarifies it's for per-call use, overriding any saved profile. However, it doesn't explicitly state when to use this vs. alternatives like find_opportunities or search_opportunities, nor when not to use it.

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