Vysion

search_email_in_im_database

Search IM database for an email address. Find if it appears in Telegram, Discord or other chats.

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": {
      "email": "<email>"
    },
    "name": "search_email_in_im_database"
  }
}

Input Schema

Name	Required	Description
`gte`	No	Date in YYYY-MM-DD, ISO 8601, or Unix timestamp format
`lte`	No	Date in YYYY-MM-DD, ISO 8601, or Unix timestamp format
`page`	No
`email`	Yes	Email address
`page_size`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

B3/5.0

Behavior2/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. "Search"/"find if it appears" weakly implies a read-only lookup, but there is no statement about permissions, rate limits, whether results are presence-only or full message records, or how the paginated response behaves. For a multi-source search tool this is a substantial gap.

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-sentence purpose is front-loaded and free of padding, but it is followed by an appended "### Responses: 200 Successful Response" block that is boilerplate noise and duplicates nothing useful. Half the text does not earn its place.

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?

Five parameters, no annotations, and no output schema mean the description must explain both behavior and return shape, and it does neither. An agent knows what to search for but not what comes back or how to page through large result sets.

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 60%, with gte/lte and email documented in the schema while page and page_size carry only defaults. The description adds nothing beyond the schema — it never mentions that results can be time-bounded or paginated, so it does not compensate for the undocumented pagination parameters.

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 concrete verb and resource ("Search IM database for an email address") and scopes the domain ("Telegram, Discord or other chats"), which distinguishes it from leak/document-oriented siblings. It never names an alternative tool explicitly, so the differentiation is inferred rather than stated.

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?

Usage is only implied by the phrase "IM database" — an agent can guess this is for chat-platform presence rather than leak lookups, but there is no explicit when-to-use, when-not-to-use, or named alternative such as search_leaks_by_email or get_documents_by_email. The vague "or other chats" also leaves the searched corpus ambiguous.

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

All Vysion tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?