Gantry

Overview Schema Source Related Servers Discussions Admin

identity

Read-only

Retrieves the authenticated identity without requiring credentials, so agents can confirm who is acting before accessing or managing versioned robotics development state.

Instructions

Read the authenticated identity, without credentials.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "arguments": "<arguments>"
    },
    "name": "identity"
  }
}

Input Schema

Name	Required	Description	Default
`arguments`	Yes
`idempotency_key`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.4.0Nov 7, 2026

TDQS

C2.7/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds only the "without credentials" note, which is genuinely useful behavioral context if it means no auth is required, but it is not disambiguated and says nothing about what identity fields come back or whether the call is cached.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence, front-loaded with the verb and resource, with no filler. Its brevity is close to the problem rather than a virtue, but as a structural matter it is tight and readable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with nested request objects, zero parameter documentation, and no output schema, one sentence is not enough. An agent has no way to construct a valid arguments payload or know what the returned identity contains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the two parameters include opaque nested objects "basis" and "intent" plus an idempotency_key on a declared read-only operation. The description does not explain any of them, so an agent must guess at the shape of the required "arguments" envelope and what a basis or intent object should contain.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Read the authenticated identity" names a specific verb and resource, so the core purpose is discernible. However, the qualifier "without credentials" is ambiguous — it could mean the call needs no authentication, or that credential material is stripped from the result — and the description offers no differentiation from any of the ~45 sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no preconditions, and no mention of alternatives. An agent cannot tell from this sentence whether identity should be called at session start, per request, or only when other context tools fail.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.