Skip to main content
Glama

Tolca: business verification (KYB)

Québec contractor check (RBQ + RENA + environmental penalties + SEAO public contracts)

qc_contractor_check
Read-onlyIdempotent

Quebec contractor check before hiring, paying or subcontracting a Québec (Canada) construction contractor, in one call: RBQ licence (status, categories, restrictions), RENA listing (banned from public contracts), environmental penalties and public contracts awarded on SEAO (count, total, buyers). Verdict ok / review / blocking with reasons, source dates and an Ed25519-signed receipt (verify at /receipts/verify). Input: name, NEQ or RBQ licence number. Free over MCP (10/day shared quota); unlimited via x402 at https://tolca.tonbot.ca/v1/qc-contractor-check ($0.1).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "qc_contractor_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
neqNoNuméro d'entreprise du Québec (10 digits)
langNoLanguage of the report: fr or en
nameNoBusiness name, exact or partial
licenceNoRBQ licence number

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / lang / description
      Added value: +"Language of the report: fr or en"
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive and open-world, and the description adds substantial context beyond them: a 10/day shared free quota, a paid x402 path with URL and price, source dates on results, and an Ed25519-signed receipt with a verification endpoint. These are exactly the operational facts an agent needs before committing a call.

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-loaded with the purpose and the checked sources, then inputs, then limits and pricing — a sensible order with no filler sentences. It is a dense run-on paragraph, though; breaking the commercial/rate-limit tail from the capability statement would improve scannability.

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

Completeness5/5

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

With no output schema, the description carries the return-value burden and does so: verdict categories, reasons, source dates, and a signed receipt. Inputs, quota, paid fallback, and verification path are all covered, leaving no material gap for a call decision.

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%, so per-parameter meaning is already documented; the description nonetheless adds the important semantic that any one identifier (name, NEQ, or RBQ licence) is sufficient, which the all-optional schema does not spell out. It omits the lang parameter entirely, so it does not fully mirror the input contract.

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?

States a specific verb and resource (contractor check) and enumerates exactly what is checked: RBQ licence status/categories/restrictions, RENA listing, environmental penalties, and SEAO contract counts. The verdict vocabulary (ok / review / blocking) makes the output shape distinguishable from generic sibling lookups like qc_licence or verify_business at a glance.

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 a clear triggering context — 'before hiring, paying or subcontracting a Québec construction contractor' — which tells the agent when this applies. It stops short of exclusions or explicit routing to overlapping siblings (qc_licence, sanctions_check, verify_business), so the agent must infer whether the composite check replaces or supplements those single-source tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.