Skip to main content
Glama
CorbettCajun

SpiderFoot MCP Server

Scan Data Unique

spiderfoot_scan_data_unique

Retrieve unique scan results from SpiderFoot OSINT reconnaissance to analyze distinct findings and eliminate duplicate data for focused investigation.

Instructions

Fetch unique scan event results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
eventTypeNo

Implementation Reference

  • Core handler logic for the 'spiderfoot_scan_data_unique' tool: makes HTTP POST request to Spiderfoot API '/scaneventresultsunique' with scan ID and optional eventType to retrieve unique event results.
    async scanEventResultsUnique(args: { id: string; eventType?: string }) {
      const { data } = await this.http.post('/scaneventresultsunique', {
        id: args.id,
        eventType: args.eventType ?? 'ALL',
      });
      return data;
    }
  • src/index.ts:88-92 (registration)
    Registers the 'spiderfoot_scan_data_unique' tool with the MCP stdio server, including input schema {id: string, eventType?: string} and thin wrapper handler calling SpiderfootClient.scanEventResultsUnique.
    server.registerTool(
      'spiderfoot_scan_data_unique',
      { title: 'Scan Data Unique', description: 'Fetch unique scan event results.', inputSchema: { id: z.string(), eventType: z.string().optional() } },
      async ({ id, eventType }) => ({ content: [{ type: 'text', text: JSON.stringify(await sf.scanEventResultsUnique({ id, eventType })) }] })
    );
  • Registers the 'spiderfoot_scan_data_unique' tool with the MCP HTTP server, including input schema {id: string, eventType?: string} and thin wrapper handler calling SpiderfootClient.scanEventResultsUnique.
    server.registerTool(
      'spiderfoot_scan_data_unique',
      { title: 'Scan Data Unique', description: 'Fetch unique scan event results.', inputSchema: { id: z.string(), eventType: z.string().optional() } },
      async ({ id, eventType }) => ({ content: [{ type: 'text', text: JSON.stringify(await sf.scanEventResultsUnique({ id, eventType })) }] })
    );
  • Zod schema definition for scan data input (id: string.min(1), eventType?: string), closely matching the tool's inputSchema (used generally for scan data tools).
    const ScanDataSchema = z.object({
      id: z.string().min(1),
      eventType: z.string().optional(),
    });
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions fetching results but doesn't specify whether this is a read-only operation, if it requires authentication, rate limits, or what the output format looks like. This leaves significant gaps for a tool that likely interacts with scan data.

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

Conciseness5/5

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

The description is a single, efficient sentence with no wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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?

Given the complexity of scan data tools, no annotations, no output schema, and low parameter coverage, the description is incomplete. It doesn't explain what 'unique' entails, how results are returned, or provide enough context for safe and effective use by an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage, so parameters 'id' and 'eventType' are undocumented. The description adds no meaning beyond the schema, failing to explain what 'id' refers to (e.g., scan ID) or how 'eventType' filters results. This doesn't compensate for the low coverage.

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

Purpose3/5

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

The description 'Fetch unique scan event results' clearly states the action (fetch) and resource (unique scan event results), but it's vague about what 'unique' means and doesn't differentiate from sibling tools like 'spiderfoot_scan_data' or 'spiderfoot_scan_logs'. It provides a basic purpose but lacks specificity.

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 guidance is provided on when to use this tool versus alternatives such as 'spiderfoot_scan_data' or 'spiderfoot_scan_logs'. The description implies usage for fetching data but offers no context on prerequisites, exclusions, or comparisons with siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CorbettCajun/Spiderfoot-MCP-Server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server