Skip to main content
Glama

search_leaks_by_username

Search Vysion's leak database for a username. Returns all leaked files where this username 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": {
      "username": "<username>"
    },
    "name": "search_leaks_by_username"
  }
}

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
usernameYesUsername to search for
page_sizeNoResults per page (default 5, max 100). Keep low to avoid large responses.

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 provided, so the description carries the full burden; it does disclose that all matching leaked files are returned, which is useful behavioral context. It omits auth requirements, rate limits, result ordering, and pagination behavior, and instead spends text on auto-generated '200 Successful Response' boilerplate.

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?

The purpose statement is front-loaded and tight at two sentences. The trailing '### Responses:' block is generated HTTP boilerplate that contributes no agent-relevant information and slightly dilutes the structure.

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?

For a five-parameter search tool with no annotations and no output schema, the description should explain result shape, pagination behavior, and ordering. It leaves those gaps and substitutes generic success-response framing, so an agent lacks enough to call it confidently beyond the happy path.

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%, with gte/lte, page, page_size and username all documented in the schema itself. The description adds no meaning beyond the schema—no explanation of how the date range or pagination interacts with results—so the baseline 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?

States a specific verb and resource ('Search Vysion's leak database for a username') and clarifies the return scope ('all leaked files where this username was found'). Sibling lookups (by email, hash, ip, phone, wallet) are implicitly differentiated by the username key, though none are named.

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?

No when-to-use guidance, no exclusions, and no routing to alternatives such as search_leaks for broader queries. The only usage signal is the implied context of 'searching for a username'.

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