Retrieve current CV-CUE API session details—logged-in user, role, customer, timezone, allowed locations, base URL, and version—to confirm connectivity before making further calls.
Show the current CV-CUE API session: logged-in key/user, role, customer, timezone and allowed locations, plus the server base URL and version. Good first call to confirm connectivity.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are supplied, so the description carries the burden. 'Show' implies a read-only operation, and the connectivity-check framing adds useful behavioral context, but it does not explicitly declare that the call is non-mutating or describe any auth/permission expectations beyond noting a logged-in key/user.
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 short sentences with zero waste: the returned fields come first, and the practical usage hint is front-loaded at the end. Nothing is redundant.
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?
With no output schema and no annotations, the description compensates by enumerating what the response contains, which is the key missing piece. Slightly incomplete in not stating that it is a read-only, permission-scoped call, but strong overall for a zero-argument diagnostic tool.
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 takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description usefully clarifies that all output is derived from the active session rather than requiring input.
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 ('Show the current CV-CUE API session') and enumerates the fields returned: key/user, role, customer, timezone, allowed locations, base URL and version. It is clear, though it does not distinguish itself from the sibling cvcue_server_info, which also appears to cover server URL/version.
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?
'Good first call to confirm connectivity' gives one concrete usage scenario but no explicit when-not conditions or named alternatives (e.g., cvcue_server_info vs this tool). Usage is implied rather than fully directed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.