Returns one enriched GitHub user record by login from dataset id enum value github-users. Use datasets_github_users_search to search the GitHub users dataset.
| Name | Required | Description | Default |
|---|---|---|---|
| login | Yes | GitHub login of the user. |
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | The tool result payload (shape varies per tool; see each tool's docs resource). |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and reach are covered. The description adds that the record is 'enriched' and tied to the `github-users` dataset id, but says nothing about auth, rate limits, or what happens with an unknown login. Some added context, but modest.
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?
Two tight sentences with the purpose front-loaded and the routing hint second. Nothing redundant; every clause earns its place.
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?
An output schema exists, so return values need no explanation, and with one parameter and clear annotations the description covers what's needed. The 'dataset id enum value' phrase is slightly confusing since no dataset-id parameter exists, but otherwise complete.
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 description coverage is 100%, so the schema fully documents the single required `login` parameter. The description restates it as the lookup key but adds no format or syntax detail beyond the schema, 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 ('Returns one enriched GitHub user record') plus the retrieval key ('by login'), which distinguishes it from the sibling list/search tools. An agent can tell it retrieves a single record rather than a filtered list 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.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly routes the agent to datasets_github_users_search when a lookup-by-login is not what's wanted, giving a clear when-to-use context. It doesn't state exclusions for the nearby/facets siblings, but for this tool family the search-vs-item split is the meaningful choice.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
