Skip to main content
Glama

search_leaks_by_phone

Search Vysion's leak database for a phone number. Requires country code separately (e.g., '34' for Spain, '1' for US).

Responses:

200: Successful Response (Success Response) Content-Type: application/json

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": {
      "country_code": "<country_code>",
      "number": "<number>"
    },
    "name": "search_leaks_by_phone"
  }
}

Input Schema

NameRequiredDescriptionDefault
gteNoDate in ISO 8601 format (e.g., '2024-01-01T00:00:00Z' or 'YYYY-MM-DD')
lteNoDate in ISO 8601 format (e.g., '2024-01-01T00:00:00Z' or 'YYYY-MM-DD')
pageNoPage number
numberYesPhone number without country code
page_sizeNoResults per page (default 5, max 100). Keep low to avoid large responses.
country_codeYesCountry code without + (e.g., '34' for Spain, '1' for US)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden, yet it does not state that this is a read-only lookup, what the returned leak records contain, whether access is rate-limited or credentialed, or how pagination behaves. The trailing '### Responses: **200**' boilerplate adds nothing beyond a generic success code.

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

Conciseness3/5

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

The two substantive sentences are short and front-loaded, but the country-code sentence duplicates the schema, and the appended HTTP response block is pure noise that lengthens the definition without informing tool selection.

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

Completeness2/5

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

With six parameters, no annotations, and no output schema, an agent needs the description to explain what a leak record looks like and how results are paged; instead it stops at the input constraint and a canned 200 response, leaving return-shape and behavioral expectations undocumented.

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 every parameter already carries a description, including the country-code-without-plus format and the page_size default/max. The description's country code examples merely repeat the schema, and it says nothing about the gte/lte date filters or paging semantics beyond what is documented there.

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 states a specific verb and resource: search Vysion's leak database for a phone number. The resource is narrow enough that an agent can distinguish it from search_leaks_by_email or search_documents without further help, though it never explicitly contrasts itself with search_leaks or get_phone_info.

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 only guidance is a mechanical constraint that the country code must be supplied separately, with examples. There is no statement of when to use this versus other phone-related siblings (get_phone_info, get_documents_by_phone) or when the tool is inappropriate.

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