Skip to main content
Glama

Match names (probabilistic)

match_names_probabilistic
Read-onlyIdempotent

Scores two counterparty names with Jaro-Winkler similarity to verify whether they represent the same party, tolerating typos and legal suffix variations.

Instructions

Score two counterparty names using Jaro-Winkler string similarity.

Purpose: Computes similarity in [0, 1] between two company or individual names, tolerating typographical variations and legal suffix abbreviations (e.g. 'Corp' vs 'Corporation Inc').

When to use:

  • When verifying whether two counterparty or entity names represent the same party.

  • When evaluating name similarity thresholds for automated matching rules.

When NOT to use:

  • Scores counterparty name strings in isolation rather than full multi-signal transaction records; use reconcile or explain_match for full records.

  • Accepts string inputs only.

Behavioral transparency: Pure, deterministic string calculation; read-only and idempotent.

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": {
      "name_a": "<name_a>",
      "name_b": "<name_b>"
    },
    "name": "match_names_probabilistic"
  }
}

Input Schema

NameRequiredDescriptionDefault
name_aYesFirst counterparty name.
name_bYesSecond counterparty name.
thresholdNoSimilarity in [0, 1] at or above which the pair is a match.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.0.5

TDQS

A4.6/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the 'read-only and idempotent' sentence largely restates structured data. What the description does add is that the computation is pure and deterministic with no external lookup, plus the tolerance semantics of the scoring, which is genuine context beyond the annotations.

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?

Well front-loaded: the one-line purpose precedes labeled sections for usage, exclusions, and behavior. The labeled-section format costs a little vertical space and the closing 'read-only and idempotent' clause duplicates the annotations, but no sentence is filler.

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?

For a three-parameter, single-calculation tool with a full output schema and complete annotation coverage, this covers everything an agent needs: what it computes, the score range, the tolerances, when to prefer siblings, and the input type restriction. Return-value detail is correctly left to the output schema.

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?

Schema coverage is 100%, so the baseline is 3; the description earns above that by explaining what the [0, 1] score means and that legal-suffix and typographical variation are absorbed, implying callers can pass raw names without pre-normalizing. It does not, however, discuss the threshold parameter's effect in the description itself.

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 — 'Score two counterparty names using Jaro-Winkler string similarity' — and immediately bounds the output to [0, 1]. It also names the tolerance behavior (typos, 'Corp' vs 'Corporation Inc'), which tells an agent exactly what class of comparison this tool handles.

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?

Provides explicit 'When to use' and 'When NOT to use' sections, and names the alternatives (reconcile, explain_match) with the condition that selects them: full multi-signal records rather than isolated name strings. It also states the hard input constraint ('accepts string inputs only').

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.