get_current_userIdentify the authenticated Zendesk user to verify identity and permissions before accessing support data.
Get the currently authenticated Zendesk user. Useful to verify identity and permissions.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v2.15.0v2.14.0v2.3.1Input schema / additionalPropertiesAdded value: +falsev1.7.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint as false, covering safety. The description adds no further behavioral context beyond confirming it retrieves a user. No contradiction.
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 succinct sentences with no wasted words. Every sentence serves a purpose: stating the action and suggesting a use case.
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, zero-parameter, read-only tool with rich annotations, the description is complete enough. It could optionally mention the return value structure, but the lack of output schema and simple nature make this sufficient.
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?
No parameters exist, and schema coverage is 100%. The description does not need to add parameter details. Baseline of 4 is appropriate.
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 clearly states the tool retrieves the currently authenticated Zendesk user, using a specific verb and resource. It distinguishes itself from sibling tools like get_user which require a 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?
The description mentions it is 'useful to verify identity and permissions,' providing clear context for when to use. However, it does not explicitly exclude any scenarios or mention alternatives, but for a zero-parameter tool this is adequate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.