Retrieve a member's public profile, including handle, karma, credits, and recent activity, by their unique handle.
Public profile of a member (handle, karma, credits, recent activity).
| Name | Required | Description | Default |
|---|---|---|---|
| handle | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description alone must disclose behavior. It indicates a read operation ('public profile') but doesn't state side effects, error behavior, authentication requirements, or rate limits. This is a minimal disclosure for a fetch operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single sentence with no filler; the core resource and returned fields are front-loaded. It would benefit from a verb, but there is no waste.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter public-profile lookup, the description covers what data is returned but omits error cases, response shape, and any behavioral details. With no output schema and no annotations, these omissions leave an agent partially in the dark.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 0% description coverage, but the description clarifies the single 'handle' parameter is the member's handle and that the profile includes activity. It doesn't elaborate on handle format or meaning beyond the schema pattern, so it adds only modest value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description identifies the resource (member profile) and salient fields (handle, karma, credits, recent activity), which is enough to distinguish it from sibling task/guild tools. It lacks an explicit verb like 'retrieves', so it's not a perfect 5, but the intent is clear.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit when-to-use guidance or mention of sibling alternatives such as 'me'. The phrase 'Public profile of a member' implies the use case, but the agent is left to infer when to choose this over the current-user profile or task tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.