devnull_get_userRetrieve a /dev/null user's public profile by GitHub username, including bio, links, commit activity, and follower and following counts.
Public profile of a /dev/null user by GitHub username: bio, links, commit, follower and following counts.
| Name | Required | Description | Default |
|---|---|---|---|
| username | Yes | GitHub username, with or without a leading @. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds that the data is the public profile and lists which counters come back, which is useful context beyond annotations. It says nothing about missing/unknown usernames or rate limiting on the external source.
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 front-loaded sentence with the resource first and the returned fields after the colon; no filler or redundancy.
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 one-parameter read tool with no output schema, the description conveys the subject and the returned field set, which is enough to call it correctly. The one real gap is the missing contrast with devnull_whoami, which shares the same conceptual space.
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?
Schema coverage is 100% and the schema already describes the username and the optional leading '@'. The description only restates 'by GitHub username', adding no new format or edge-case detail, so the baseline 3 applies.
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?
States a specific verb+resource: fetches a public user profile by GitHub username, and enumerates the fields returned (bio, links, commit/follower/following counts). It never distinguishes itself from the sibling devnull_whoami, which an agent could plausibly confuse with 'my own profile'.
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 statement of when to use this versus devnull_whoami or the commit-related siblings, and no prerequisites or error conditions (e.g. unknown username). Usage must be inferred from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.