Skip to main content
Glama

HeyIdentity

add_custom_claim

Adds a custom claim emitted for every user. claim: { name, value, target?: both|id_token|access_token }.

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>",
      "claim": "<claim>"
    },
    "name": "add_custom_claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
claimYesThe custom claim. 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.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It does disclose one meaningful behavioral fact: the claim is emitted for every user, implying global effect rather than per-client scoping. It says nothing about what happens on a duplicate claim name, whether the change takes effect immediately, required permissions, or whether existing tokens are affected.

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 front-loaded with the action and scope in one sentence, and the compact schema echo is readable. The second clause duplicates structured schema content, which is minor waste but not enough to obscure the main point.

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 two-parameter mutation tool with no annotations and no output schema, the description covers the purpose and the payload shape adequately. It is incomplete on the mutation's side effects and failure modes, which matter for a write operation that affects every user.

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, value, and the target options including the 'both' default. The description restates the claim shape and target values without adding syntax, format, or validation meaning, so the baseline of 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?

The description states a specific verb and resource ('Adds a custom claim') plus the scope ('emitted for every user'), which tells an agent this is the create path for per-user custom claims. It does not explicitly distinguish itself from edit_custom_claim, remove_custom_claim, or set_standard_claims, so the custom-vs-standard boundary is left implicit.

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 explicit when-to-use or when-not-to-use guidance, and no alternative is named. The presence of edit_custom_claim, remove_custom_claim, and set_standard_claims in the sibling set makes the missing routing guidance a real gap, since an agent must infer that 'add' means the claim does not yet exist.

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