MCP Agent Mail

whois

Retrieve an agent's enriched profile and optional recent archive commits to verify identity and activity for coordination.

Instructions

Return enriched profile details for an agent, optionally including recent archive commits.

Discovery

To discover available agent names, use: resource://agents/{project_key} Agent names are NOT the same as program names or user names.

Parameters

project_key : str Project slug or human key. agent_name : str Agent name to look up (use resource://agents/{project_key} to discover names). include_recent_commits : bool If true, include latest commits touching the project archive authored by the configured git author. commit_limit : int Maximum number of recent commits to include.

Returns

dict Agent profile augmented with { recent_commits: [{hexsha, summary, authored_ts}] } when requested.

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": {
      "project_key": "<project_key>",
      "agent_name": "<agent_name>"
    },
    "name": "whois"
  }
}

Input Schema

Name	Required	Description	Default
`format`	No
`agent_name`	Yes
`project_key`	Yes
`commit_limit`	No
`registration_token`	No
`include_recent_commits`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.4Sep 30, 2026

TDQS

A4.1/5.0

Behavior3/5

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

With no annotations, the description carries the full burden and does disclose the return shape (a dict augmented with recent_commits when requested) and the conditional behavior of include_recent_commits. It omits anything about read-only/idempotency, permissions, or auth implications (e.g., what registration_token does), leaving meaningful behavioral gaps.

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?

The definition is front-loaded with the core purpose and organized into Discovery/Parameters/Returns sections that each add value. It is somewhat long, and the Returns section partially duplicates the output schema, but nothing is egregiously wasteful.

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?

The tool is a read-style profile lookup with an output schema present, so return values need not be spelled out (and are anyway). Discovery guidance and commit-option behavior make it largely self-sufficient; the residual gap is the undocumented format and registration_token parameters.

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?

Schema description coverage is 0%, so the description must compensate, and it does add real meaning for the core parameters: project_key, agent_name (with a discovery pointer), include_recent_commits, and commit_limit semantics are all explained. It still leaves two parameters (format and registration_token) undocumented, so it is not fully complete.

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 opening sentence states a specific verb+resource ('Return enriched profile details for an agent, optionally including recent archive commits'), and the Discovery section explicitly warns that agent names are NOT program or user names, disambiguating it from siblings. An agent can tell this apart from fetch_summary or list_window_identities without opening any schema.

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?

It gives clear operational context for discovery via resource://agents/{project_key} and clarifies the identity-space constraint. However, it never states when to prefer this over adjacent siblings like fetch_summary or list_window_identities, so it lacks explicit exclusions/alternatives.

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