Skip to main content
Glama

metaphone_encode

Read-onlyIdempotent

Encode words into Metaphone phonetic codes or compare two words phonetically to check if they sound alike, useful for name matching and deduplication.

Instructions

Encode words using the Metaphone phonetic algorithm, optionally comparing two words.

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": {
      "text": "<text>"
    },
    "name": "metaphone_encode"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesWord(s) to encode.
compareNoSecond word to compare phonetically.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorldHint and non-destructive, so the safety profile is covered. The description adds only that comparison is optional and that the algorithm is Metaphone; it says nothing about determinism of the output, casing/character handling, or what a comparison yields.

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?

One sentence, front-loaded with the core action and no filler. The trailing compare clause is slightly bolted-on but overall highly efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 should say what an encode returns (a phonetic code string) and, critically, what the compare mode returns (a boolean match or both codes). Neither is stated, leaving the return shape ambiguous for a tool whose main value is the comparison mode.

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 both `text` and `compare` documented in the schema itself. The description's 'second word to compare phonetically' restates the schema's own wording and adds only the word 'optionally', so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (encode) and resource (words via the Metaphone phonetic algorithm) and flags the optional comparison mode. It does not distinguish itself from the closest sibling, soundex_encode, which an agent might reasonably confuse it with.

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

Usage Guidelines3/5

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

The phrase 'optionally comparing two words' implies a second use case (phonetic matching) but gives no explicit when-to-use, when-not-to-use, or pointer to soundex_encode / phonetic_spell as alternatives. Usage must be inferred from the capability statement.

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

Deploy Server

Other Tools