Skip to main content
Glama

search_leaks_by_ip

Search Vysion's leak database for an IP address (IPv4 or IPv6). Returns all leaked files where this IP was found.

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": {
      "ip_address": "<ip_address>"
    },
    "name": "search_leaks_by_ip"
  }
}

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
page_sizeNoResults per page (default 5, max 100). Keep low to avoid large responses.
ip_addressYesIPv4 or IPv6 address (e.g., '192.168.1.1')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose that results are all leaked files matching the IP, which is useful return-scope context, but says nothing about authentication, rate limits, result caps, or ordering. The appended HTTP response boilerplate adds no behavioral value.

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 core sentence is tight and front-loaded, but the trailing '### Responses: **200**: Successful Response (Success Response) Content-Type: application/json' block is boilerplate that consumes space without informing the agent.

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?

With five parameters, no annotations, and no output schema, the description should explain how the date range and pagination affect results and what the returned records look like. It gives only a one-line summary of the result set, leaving return shape and filtering behavior to inference.

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 description coverage is 100%, so the schema already documents ip_address, gte/lte date bounds, page, and page_size. The description only restates that the address may be IPv4 or IPv6, adding no new meaning about date filtering or pagination semantics.

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 and resource: searches Vysion's leak database for an IP address, and describes the result set (leaked files where the IP was found). The 'by_ip' scoping implicitly distinguishes it from the many sibling search_leaks_by_* tools, though it never names them.

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?

There is no when-to-use guidance, no exclusions, and no reference to alternatives such as search_leaks for broader queries. The only signal is the implied 'use this when you have an IP', which an agent must infer.

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