Skip to main content
Glama

HeyIdentity

edit_user

Edits a user; fields left out keep their value, and claims, when given, replace the user's claims.

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": {
      "configuration_id": "<configuration_id>",
      "key": "<key>",
      "changes": "<changes>"
    },
    "name": "edit_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesThe key of the user to edit.
changesYesThe fields to change. A fictional test user. On edit, fields left out keep their value; claims, when given, replaces the user's claims.
configuration_idYesThe configuration id (from create_tenant or get_tenant).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose two consequential behaviors: omitted fields are preserved (patch semantics) and supplied claims replace rather than merge, which an agent must know before calling. It omits permission/plan requirements, whether the key is immutable after creation, and what the call returns.

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 tight sentence with the mutation scope front-loaded and no wasted wording. It is arguably under-specified rather than padded, which is a completeness issue rather than a structure one.

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

Completeness3/5

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

For a three-parameter mutation tool with no annotations and no output schema, the description covers the two riskiest semantics (partial update, claim replacement). It leaves open whether edits require a paid plan, whether the user key can change, and what is returned, which the agent must infer from the schema alone.

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

Parameters3/5

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

Schema description coverage is 100%, so the nested change fields are already fully documented, including the claim_targets and sign_in_outcome semantics. The description restates the patch and claims-replacement rules but adds no format or syntax detail beyond the schema, so the baseline 3 applies.

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

Purpose4/5

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

States a specific verb and resource ("Edits a user") plus two behavioral rules. The user-versus-client split is inferable from the name and sibling set, but the description itself does not contrast with add_user or edit_client.

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?

No explicit when-to-use guidance, no alternatives named, and no prerequisites stated. The only usage-relevant information is implicit: this is a partial-update operation because omitted fields retain their values.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources