Skip to main content
Glama

source_crosscheck

Fetch multiple source URLs and cross-check entities to separate corroborated indicators from single-source claims. Extracts emails, domains, IPs, CVEs, wallets, handles, phones and hashes.

Instructions

Fetch several source URLs and cross-check entities across them.

Accepts a comma/newline-separated list (or a JSON list). Extracts emails, domains, IPs, CVEs, wallets, handles, phones and hashes, then separates corroborated entities (2+ sources) from single-source claims. Fast HTTP mode.

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": {
      "sources": "<sources>"
    },
    "name": "source_crosscheck"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
sourcesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses the transport (fast HTTP, i.e. non-rendering), the extraction taxonomy, and the key analytical behavior of splitting corroborated entities from single-source claims. It still omits failure behavior for unreachable URLs, source-count limits, and the response shape.

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?

Front-loaded purpose sentence followed by two supporting sentences with no filler. The only friction is that the accepted-input-format note is buried mid-paragraph after the purpose rather than adjacent to the entity list, and line wrapping splits an enumerative sentence.

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?

For a tool with no annotations, no output schema, and one undocumented parameter, the description is adequate but not complete: it never describes what a result record looks like, whether results are grouped or flat, how many sources are supported, or what `query` does. An agent knows what the tool does but not exactly what it will get back.

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 0%, and the description compensates for `sources` by specifying three accepted encoding forms (comma-separated, newline-separated, JSON list). The `query` parameter is never mentioned, leaving half the inputs undocumented in both schema and description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (fetch source URLs, cross-check entities) plus the exact entity classes extracted and the corroboration rule (2+ sources vs single-source). An agent can tell precisely what this tool does and what it produces without opening the schema.

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 implied by the corroboration framing — you call it when you have multiple sources and want to separate confirmed entities from single-source claims. However, no alternative is named; 'Fast HTTP mode' hints that a slower/browser-based sibling exists for JS-heavy pages but never says so or when to prefer it.

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