Skip to main content
Glama

Phone Enrichment

run_phone_enrichment
Read-onlyIdempotent

Enriches a known phone number with associated profile data (name, email, company, LinkedIn/X profiles, carrier) when available.

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": {
      "phone": "<phone>"
    },
    "name": "run_phone_enrichment"
  }
}

Input Schema

NameRequiredDescriptionDefault
phoneYesPhone number in international format, e.g. +1234567890

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context by listing the enriched data categories and noting that results are only returned 'when available,' but it does not address lookup confidence, rate limits, or external-data limitations beyond what the annotations imply.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is one tightly written sentence that front-loads the action, resource, and output categories. There is no redundant or filler language.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter enrichment tool with no output schema, the description usefully enumerates the returned profile fields and notes that enrichment is availability-dependent. The main remaining gap is sibling scope: it does not explain how this differs from run_phone_enrichment_us, which could matter for correct tool selection.

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%, and the single phone parameter is fully documented in the schema with international-format guidance. The description adds only the notion that the phone number is 'known,' which is already implied by the enrichment purpose, so the baseline of 3 is appropriate.

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?

The description gives a specific verb and resource: it enriches a known phone number with named profile fields. However, it does not distinguish this general enrichment tool from the sibling run_phone_enrichment_us, so an agent cannot tell from the description alone whether this tool is global, non-US, or otherwise scoped.

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

Usage Guidelines2/5

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

The description implies usage by saying 'Enriches a known phone number,' but it gives no explicit when-to-use guidance, no prerequisites, and no alternatives such as run_phone_enrichment_us or run_email_enrichment. The phrase 'when available' is a data-availability caveat, not usage direction.

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