Skip to main content
Glama

Match a list of businesses

match_list
Read-onlyIdempotent

Finds which businesses of a list the person already has (a CRM export, a spreadsheet) are in Fyrmo. Each row matches by phone, email or own website, or by exact name plus canton or district; a phone or website shared by several businesses (a chain, a directory) only counts when the name tells them apart. Returns, per row (0-based), the business code and what it matched by, or why not (no_data, not_found, ambiguous, daily_limit), plus the matched businesses without their contacts. No credits; counts toward the daily search results; reveal the ones they want with reveal_contacts. Up to 200 rows per call. The list is not stored.

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": {
      "rows": "<rows>"
    },
    "name": "match_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the readOnly/idempotent annotations: discloses matching precedence, the chain/directory ambiguity rule, the per-row failure reasons (no_data, not_found, ambiguous, daily_limit), credit and daily-quota accounting, and that the list is not stored. No contradiction with readOnlyHint — nothing is written.

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, then matching rules, then return shape, then cost limits — a logical order with no filler. The return-value sentence is quite dense and packs four failure codes plus output shape into one clause, which costs some readability.

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?

No output schema exists, so the description must define return values, and it does precisely: per-row 0-based index, matched business code and match basis, or the specific non-match reason, plus matched businesses without contacts. Combined with the row cap and quota behavior, 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema coverage reported at 0%, the description carries the burden and does so substantially: it specifies which row fields drive matching (phone, email, own website, or exact name plus canton/district) and warns that shared phone/website needs name disambiguation. It stops short of format examples for each field, but the schema supplies maxLengths and some field hints.

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?

Names a specific verb and resource — finds which businesses from a supplied list are already in Fyrmo — and the parenthetical 'a CRM export, a spreadsheet' fixes the input shape. It is clearly distinguishable from list-building or search siblings because the input is the user's own list rather than a query.

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?

Explains the matching rules and routes the agent to reveal_contacts for contacts, plus states cost ('No credits; counts toward the daily search results') and the 200-row limit. It does not explicitly contrast with search_businesses or build_list when a user has no existing list, so the when-not guidance is implicit.

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.

Resources