get_connection_identityReturn the profile ID and active company ID used by this authenticated MCP connection. Use this before a paid operation when a release or audit must prove the connection is scoped to the intended Uwear account.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare the operation as read-only, idempotent, and non-destructive. The description adds useful behavioral context by specifying exactly what it returns and that it is scoped to the authenticated connection, without contradicting the annotations.
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 two sentences with no filler. The first sentence front-loads the core function, and the second adds the key usage context. Every sentence 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?
For a zero-parameter getter with rich annotations and no output schema, the description adequately explains both the return values and the operational context. Nothing critical is missing for an agent to decide when and how to invoke it.
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 and the schema is fully self-documenting with an empty properties object. The description therefore has no parameter burden to carry, and a baseline of 4 for zero-parameter tools 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 states a specific verb ('Return') and resource ('profile ID and active company ID used by this authenticated MCP connection'), making it clear what the tool does. This distinguishes it from the many get_* siblings, which operate on different resources.
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 explicitly instructs when to call this tool: 'Use this before a paid operation when a release or audit must prove the connection is scoped to the intended Uwear account.' It does not explicitly state when not to use it or name alternatives, but no sibling appears to overlap with its purpose.
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.
Most tools target distinct resources and have detailed descriptions, but several closely related families exist: create_credit_checkout_session vs mcp_create_credit_checkout_session, the propose_brief/confirm_brief/update_brief lifecycle, and the many avatar/upload entry points. An agent must read long caveats carefully to avoid selecting the wrong tool.
The vast majority of tool names follow a predictable snake_case verb_noun pattern (list_*, get_*, create_*, update_*, propose_*). The mcp_* prefix group and varied creation verbs (create/upload/save/add/generate) are minor deviations, though mcp_create_credit_checkout_session duplicating create_credit_checkout_session adds some confusion.
With 67 tools, this is an extreme mismatch by the rubric's own 50+ threshold, far beyond the typical 3-15 well-scoped range. Many tools are narrow lifecycle steps such as two-phase local uploads, app-only montage internals, and multiple ArtDirection authoring variants, making the agent-facing surface very heavy.
The core generation, brief, montage, and QA workflows are covered thoroughly with polling and result retrieval. However, notable lifecycle gaps exist: outfits, locations, avatars, and tags mostly have create/list/get but no update or delete, and delete_template is the only delete tool in the entire set.