Retrieve the current user's ID to identify the authenticated user in Yandex Webmaster.
Get current user info (user ID)
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "ywm_get_user"
}
}| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden for behavioral disclosure. It does not mention authentication requirements, error scenarios (e.g., unauthenticated state), or return format. The tool likely requires authentication; this should be stated.
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?
The description is extremely concise with a single phrase. While no word is wasted, it is too minimal and lacks structured information. It could be a full sentence with additional context without losing conciseness.
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?
Given no parameters and an empty schema, the description provides the essential purpose but omits details like what 'user info' includes beyond ID, and whether the output is simple or structured. With no output schema, more detail would improve completeness.
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 tool has zero parameters, achieving 100% schema coverage by default. The description adds value by specifying the output includes 'user ID', which clarifies what 'user info' means. Baseline for no parameters is 4, and the description meets that by providing useful context beyond the empty schema.
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 'Get current user info (user ID)' uses a specific verb ('Get') and resource ('current user info'), clearly distinguishing it from sibling tools like 'ywm_get_host' or 'ywm_get_sitemap'. It uniquely identifies the tool's function of retrieving the current authenticated user's information, including the user ID.
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 guidance is provided on when to use this tool versus alternatives. For a simple identity tool, it would benefit from context like 'Use this to identify the current user before performing operations that require user context.' The description lacks any usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.