Skip to main content
Glama

Tolca: business verification (KYB)

qc-licence

qc_licence
Read-onlyIdempotent

Quebec contractor licence check (RBQ): contractor license verification in one call, cheapest tier. Is this Québec contractor's RBQ licence ACTIVE right now? Returns active true/false, licence number, name, NEQ, city, restriction flag and authorized work categories. Use to vet many contractors fast; use qc-contractor-check for RENA and penalties. Input: name, NEQ or RBQ licence number. Costs $0.01 USDC per call (x402 v2, Base or Solana). Send the HTTP header PAYMENT-SIGNATURE with your x402 payment, or call POST https://tolca.tonbot.ca/v1/qc-licence with an x402 client.

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_licence"
  }
}

Input Schema

NameRequiredDescriptionDefault
neqNoNuméro d'entreprise du Québec (10 digits)
nameNoBusiness name, exact or partial
licenceNoRBQ licence number

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already indicate a read-only, idempotent, non-destructive, open-world check. The description adds important behavior beyond that: cost per call, x402 payment via PAYMENT-SIGNATURE header, endpoint, and the exact fields returned including active status, licence number, NEQ, city, restriction flag, and authorized work categories.

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?

The description is front-loaded with the core question and return values, then use guidance, alternative, input, and payment details. It is efficient overall, though the opening repeats licence-check wording and the payment instructions make it longer than a minimal definition.

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?

There is no output schema, but the description lists the key return fields and the active true/false answer. It also covers payment/auth requirements, cost, endpoint, alternative tool, and input identifiers, which is complete enough for an agent to invoke it correctly.

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 name, NEQ, and licence number formats. The description adds a small amount by saying input can be name, NEQ, or RBQ licence number, but it does not clarify identifier precedence or whether one identifier alone is sufficient.

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 states a specific verb and resource: RBQ Quebec contractor licence verification. It also names the sibling tool qc-contractor-check and explains that this tool is for active licence status while the sibling covers RENA and penalties, making the distinction explicit.

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

Usage Guidelines5/5

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

It gives a clear use case: vet many contractors fast at the cheapest tier. It also names an alternative, qc-contractor-check, and the condition for using it: when RENA and penalties are needed.

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.