Skip to main content
Glama

Tolca: business verification (KYB)

company-enrich

company_enrich
Read-onlyIdempotent

Company profile from a domain or name in ONE call, for sales and research agents: what the company does, industry, services, service area, address, phones and emails published by the company (each with the page it came from), social links, plus official screening (registries, US, UK, EU and Canadian sanctions lists). Read live from the company's own website, no third-party database. No website found = HTTP 404 = no charge. Input: domain or name, optional city, country, lang (en|fr). Businesses only. Costs $0.02 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/company-enrich 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": "company_enrich"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity, to find the right company when several share the name
langNoLanguage of the profile: en or fr
nameNoCompany name, used to find the website when no domain is given
domainNoCompany website or domain, e.g. acme.com
countryNoISO 3166 alpha-2
official_checksNoAlso run official checks: sanctions lists, registries and licences

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / city / description
      Added value: +"City, to find the right company when several share the name"
    • addedInput schema / properties / lang / description
      Added value: +"Language of the profile: en or fr"
    • addedInput schema / properties / official_checks / description
      Added value: +"Also run official checks: sanctions lists, registries and licences"
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only cover read-only/idempotent/open-world, but the description adds what matters operationally: the data is read live from the company's own site with no third-party database, official screening can be toggled via a parameter, and a failed lookup returns 404 at no charge. It also discloses the $0.02 USDC cost, x402 v2 payment scheme, and the PAYMENT-SIGNATURE header required for invocation.

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-loads the value and output contents before mechanics, and every clause carries information. The payment and endpoint details are dense but necessary for invocation; the sentence is long and could be split for scannability, which is the main deduction.

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, so the description compensates by enumerating the returned fields, noting provenance ('each with the page it came from'), and describing the no-result case. The cost, payment protocol, and endpoint are all present, so an agent has everything needed to call 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 explains domain, name, city, country, lang, and official_checks. The description restates the input set ('domain or name, optional city, country, lang (en|fr)') and confirms screenings are optional, adding little beyond the structured fields. Baseline 3 applies when the schema does the heavy lifting.

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 ('Company profile from a domain or name in ONE call') and enumerates the payload: what the company does, industry, services, address, phones, emails, social links, sanctions screening. It is clearly distinguishable from siblings like sanctions_check (screening only) and verify_business.

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 audience context ('for sales and research agents'), an explicit scope limit ('Businesses only'), and a precondition ('No website found = HTTP 404 = no charge'). It does not explicitly say when to prefer this over verify_business or sanctions_check for a screening-only need, which keeps it short of a 5.

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.