Fetch the current user's profile via the QRStuff API.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| idclient | Yes | ||
| timezone | No | ||
| username | No | ||
| last_name | No | ||
| first_name | No | ||
| address_city | No | ||
| phone_number | No | ||
| address_state | No | ||
| business_name | No | ||
| address_street | No | ||
| address_country | No | ||
| address_postcode | No | ||
| address_country_code | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description adds only 'via the QRStuff API,' which is implementation detail rather than meaningful behavioral context such as auth requirements or rate limits.
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 a single front-loaded sentence with no wasted words. It is appropriately sized for a simple zero-parameter read tool.
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 current-user profile fetch, the description is mostly complete: it says what is fetched and that an output schema exists to explain return values. It could mention authentication or account context, but the annotations and output schema cover most remaining needs.
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, so there is no parameter semantics to explain. The baseline for a zero-parameter tool is 4, and no additional parameter meaning is needed.
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 and resource: fetch the current user's profile. It is clear what the tool returns, though it does not explicitly distinguish itself from sibling account-related tools like get_account_overview.
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?
Provides no when-to-use guidance, prerequisites, or alternatives. The purpose implies usage, but the description gives no explicit context for selecting this tool over sibling account/profile tools.
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.
