Skip to main content
Glama
badchars

osint-mcp-server

by badchars

osint_list_sources

Lists available OSINT data sources with their configuration status, API requirements, and included tools to verify what sources are ready for use.

Instructions

List all OSINT data sources, their availability, API key requirements, and tool counts. Use this to check which sources are configured.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function checkSources that implements the logic for osint_list_sources.
    export async function checkSources(ctx: ToolContext): Promise<SourceInfo[]> {
  • Registration of the osint_list_sources tool in the tool definition list.
    const osintListSourcesTool: ToolDef = {
      name: "osint_list_sources",
      description: "List all OSINT data sources, their availability, API key requirements, and tool counts. Use this to check which sources are configured.",
      schema: {},
      execute: async (_args, ctx) => json(await checkSources(ctx)),
    };
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 implies this is a read-only operation (listing sources) and mentions configuration checking, but it doesn't disclose behavioral traits like rate limits, authentication needs beyond API key requirements, or what happens if no sources are configured. The description adds some context but lacks depth for a higher score.

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 two sentences that are front-loaded with the main purpose and followed by usage guidance. Every sentence adds value without waste, making it highly concise and well-structured for an agent to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (simple listing with no parameters) and lack of annotations or output schema, the description is reasonably complete. It explains what the tool does and when to use it. However, it could be more comprehensive by detailing the output format or potential errors, which would improve completeness for a score of 5.

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

Parameters4/5

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

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the inputs. The description doesn't need to add parameter information, and it appropriately doesn't mention any parameters. A baseline of 4 is applied since no parameters are present, as the description doesn't introduce confusion or redundancy.

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?

The description clearly states the action ('List all OSINT data sources') and specifies what information is included ('availability, API key requirements, and tool counts'), making the purpose explicit. However, it doesn't explicitly differentiate from sibling tools like 'osint_domain_recon' or other OSINT-related tools, which would be needed for a score of 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use this tool ('Use this to check which sources are configured'), which helps the agent understand its purpose. However, it doesn't explicitly state when not to use it or name specific alternatives among the sibling tools, preventing a score of 5.

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/badchars/osint-mcp-server'

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