Skip to main content
Glama
Sign In
Clearfront MCP Server

Clearfront MCP Server

by scottmartinanderson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

search_maigret

Search a username across 3,400+ websites to discover associated accounts and extract public profile details. For authorized use only.

Instructions

Broad username/identity discovery across 3,400+ sites via maigret (also extracts profile details). Authorized use only: your own assets or a target you are authorized to assess. Passive, public-source collection.

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_maigret"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYes
json_outputNoReturn result as structured JSON.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.7.2
  2. Removedv2.7.2
  3. First observedv2.5.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description must carry full weight. It indicates passive, read-only behavior and authorization requirements, but lacks details on rate limits, error handling, or specifics of profile detail extraction.

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?

Two sentences efficiently convey purpose and usage constraints without extraneous information, front-loading the core action.

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?

Given the tool's complexity (3,400+ sites), lack of output schema, and sibling competition, the description is brief and omits return format, result interpretation, and what 'profile details' entails.

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?

Schema coverage is 50% (json_output described, username not). The description adds no parameter-specific guidance, such as expected username format or behavior of json_output, failing to compensate for the schema's gap.

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?

The description clearly states the tool performs broad username/identity discovery across 3,400+ sites using maigret, and distinguishes itself from sibling tools like search_username by emphasizing breadth and profile detail extraction.

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 explicitly mandates authorized use only and notes passive, public-source collection, providing clear context for when the tool is appropriate. However, it does not contrast with alternatives or state when not to use.

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

Deploy Server

Other Tools