Skip to main content
Glama

Tolca: business verification (KYB)

company-fit

company_fit
Read-onlyIdempotent

Is this company worth contacting FOR YOU? Everything in company-enrich, plus a fit verdict for your offer and goal: good / maybe / poor, a 0-100 score, reasons grounded in facts from the company's website, and an opening line that references one of those facts. Input: domain or name, plus for: { seller (who you are and what you sell), goal (sales | partnership | supplier | hiring | investment | other), optional ideal_customer }. No website found = no charge. Costs $0.03 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-fit with an x402 client.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "for": "<for>"
    },
    "name": "company_fit"
  }
}

Input Schema

NameRequiredDescriptionDefault
forYesWho you are and what you want from this company
cityNoCity, to find the right company when several share the name
langNoLanguage of the answer: 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 country code
official_checksNoAlso run official checks: sanctions lists, registries and licences

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / city / description
      Added value: +"City, to find the right company when several share the name"
    • addedInput schema / properties / country / description
      Added value: +"ISO 3166 alpha-2 country code"
    • addedInput schema / properties / for / description
      Added value: +"Who you are and what you want from this company"
    • addedInput schema / properties / for / properties / goal / description
      Added value: +"Your goal with this company: sales, partnership, supplier, hiring, investment or other"
    • addedInput schema / properties / for / properties / ideal_customer / description
      Added value: +"Your ideal customer, used to judge the fit"
    • addedInput schema / properties / lang / description
      Added value: +"Language of the answer: en or fr"
    • addedInput schema / properties / name / description
      Added value: +"Company name, used to find the website when no domain is given"
    • addedInput schema / properties / official_checks / description
      Added value: +"Also run official checks: sanctions lists, registries and licences"
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, openWorld and non-destructive, and the description adds substantial context beyond them: cost of $0.03 USDC per call, x402 payment mechanics with the PAYMENT-SIGNATURE header, and the favorable 'no website found = no charge' policy. It stops short of describing latency, rate limits, or answer shape beyond the listed fields, so it is strong but not exhaustive.

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 lead question is front-loaded and the value proposition precedes payment details. It is dense and largely earn-place, though the payment instructions and input list are packed into run-on sentences that could be split or trimmed for scanning.

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 still enumerates the return payload (verdict, 0-100 score, grounded reasons, opening line), states cost and refund behavior, and specifies how to pay. For a paid, open-world enrichment tool, an agent has what it needs to call it correctly and anticipate the charge.

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 coverage is 100%, with every parameter carrying its own description, so the schema already does the heavy lifting. The description restates the main input pattern (domain or name, plus 'for' with seller, goal and optional ideal_customer) but adds no syntax, format, or fallback detail beyond what is documented in the schema; city, country, lang and official_checks go unmentioned.

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?

Opens with a specific question the tool answers and states exactly what it returns: 'Everything in company-enrich, plus a fit verdict... good / maybe / poor, a 0-100 score, reasons grounded in facts... and an opening line.' It explicitly positions itself relative to the sibling company_enrich as a superset, so an agent can discriminate without reading either schema.

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 gives a clear context for use ('worth contacting FOR YOU', driven by the 'for' object with seller and goal), which implies the alternative company_enrich is for fact-only lookups. It does not state explicit when-not conditions or name the alternative tool outright, keeping it at a 4 rather than 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.