Skip to main content
Glama

HeyIdentity

edit_custom_claim

Edits a custom claim's value or target; fields left out keep their value. changes: { value?, target? }.

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>",
      "name": "<name>",
      "changes": "<changes>"
    },
    "name": "edit_custom_claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe name of the claim to edit.
changesYesThe fields to change. A custom claim emitted for every user.
configuration_idYesThe configuration id (from create_tenant or get_tenant).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses merge semantics (omitted fields retain their value) but says nothing about permission requirements, whether an edit is reversible, or what the response contains for this mutation.

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?

The definition is one short front-loaded sentence followed by a compact field shorthand, with no filler. The pseudo-schema fragment at the end is slightly cryptic but still short and readable.

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 core merge behavior adequately. It still leaves the agent without any information on permissions, error conditions, or the result of the operation.

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 schema already documents configuration_id, name, and each field of changes. The trailing 'changes: { value?, target? }' restates the schema rather than adding new meaning, so baseline 3 is appropriate.

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 custom claim's value or target'), which clearly separates it from add_custom_claim and remove_custom_claim by name alone. It does not explicitly name those siblings, so the differentiation is inferred rather than stated.

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

Usage Guidelines3/5

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

The phrase 'fields left out keep their value' implies a partial-update use case, which helps an agent decide when this tool is appropriate. However, there is no explicit when-to-use guidance, no mention of alternatives, and no stated prerequisites such as needing an existing claim or configuration.

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