Skip to main content
Glama
Sign In
Clearfront MCP Server

Clearfront MCP Server

by scottmartinanderson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

search_gravatar

Retrieve public Gravatar profile information (avatar, name, bio, location, linked accounts) from an email address. Authorized use only.

Instructions

Look up an email's public Gravatar profile: avatar, display name, bio, location, and linked/verified accounts. 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": {
      "email": "<email>"
    },
    "name": "search_gravatar"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYes
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

A4.2/5.0
Behavior4/5

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

With no annotations, the description discloses that the tool is passive and public-source, implying no destructive side effects. It lists the type of data returned, which provides transparency beyond the name alone.

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?

Three concise sentences: first states purpose and output, second gives usage guideline, third notes passive nature. No filler or redundant information.

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?

For a simple lookup tool with two parameters, the description covers purpose, authorized use, data returned, and operational nature. Lacks mention of behavior when email has no Gravatar, but overall adequate.

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?

The schema has 50% coverage (only json_output has a description). The description does not elaborate on the email parameter beyond the verb 'look up', but the parameter name is self-explanatory. The json_output parameter is already described in the schema.

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 verb 'Look up', the resource 'email's public Gravatar profile', and lists specific data fields (avatar, display name, bio, location, linked/verified accounts). It distinguishes from sibling tools by specifying Gravatar as the service and notes it as passive, public-source collection.

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?

Includes explicit authorization requirement ('Authorized use only: your own assets or a target you are authorized to assess') and notes the passive nature. However, it does not provide when-not-to-use or compare with alternatives like search_email.

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