Tolca MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TOLCA_MCP_URL | No | URL of the hosted Tolca MCP server to bridge to. Defaults to the free public server. Point this bridge at the paid server with TOLCA_MCP_URL=https://tolca.tonbot.ca/mcp to get extra tools (web_search, business_verification, etc.), paid per call in USDC on Base. | https://tolca.tonbot.ca/mcp/public |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| qc_contractor_checkA | Check a Québec construction contractor against four official public data sources in one call: active RBQ licence (status, restrictions, bond, authorized work categories), RENA (businesses barred from public contracts and public subcontracts), environmental administrative penalties (MELCCFP) and public contracts awarded on SEAO (count, total amount, main public buyers, last 12 months). Returns a verdict ok / review / blocking / not_found with reasons, sources and extraction dates. Use when the user asks whether a Québec contractor, subcontractor or renovation company is licensed, trustworthy or eligible for public contracts. Provide neq, licence or name. |
| qc_licenceA | Fast lookup: does this Québec business hold an ACTIVE RBQ (Régie du bâtiment du Québec) construction licence right now? Returns active true/false, licence number, legal name, NEQ, municipality, restriction flag and authorized work categories. Good for checking several contractors one after another. For the RENA public-contract ban and environmental penalties, use qc_contractor_check. Provide neq, licence or name. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools overlap on RBQ licence checks, but descriptions clearly distinguish qc_licence as a fast single-source lookup and qc_contractor_check as a comprehensive multi-source verification. The explicit pointer from qc_licence to qc_contractor_check for additional checks reduces potential confusion.
Both names use snake_case and a 'qc_' prefix, but the structure is inconsistent: qc_licence is a simple noun while qc_contractor_check is noun_verb. There is no predictable verb_noun pattern, though the names remain readable.
Only two tools are provided, which feels thin for a contractor verification domain that could support separate checks per data source or batch operations. However, the comprehensive tool consolidates most needs, making the count borderline rather than severely lacking.
The tools cover four key public data sources (RBQ, RENA, environmental penalties, SEAO) and support lookup by NEQ, licence, or name. This is strong coverage for the stated purpose, though other potential checks like workplace safety or legal disputes are not addressed.