Skip to main content
Glama

HeyIdentity

remove_custom_claim

Destructive

Removes a custom claim.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe name of the claim to remove.
configuration_idYesThe configuration id (from create_tenant or get_tenant).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, so the description's only job is to add context beyond that, and it adds none: it doesn't say whether removal is irreversible, what happens to tokens or existing users carrying the claim, or whether other claims are affected. A single restatement of the annotation-level behavior earns a 2.

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

Conciseness3/5

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

The single sentence is efficient and front-loaded, but its brevity reflects under-specification rather than disciplined concision given the destructive nature of the operation.

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 destructive, configuration-scoped mutation with no output schema, the description omits irreversibility, error behavior, and the consequences of removing an in-use claim. The complete input schema partially compensates, but the behavioral picture is not complete enough for an agent to act confidently.

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%, with both name and configuration_id documented in the schema, so the baseline is 3. The description adds no additional meaning about how the parameters interact or what happens when a claim name does not exist.

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 ("Removes a custom claim"), which distinguishes it from the add_custom_claim and edit_custom_claim siblings by operation. It names no sibling explicitly and gives no scope detail, so it stops short of a 5.

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 prerequisites (e.g. requiring configuration_id from create_tenant/get_tenant), and no mention of alternatives such as edit_custom_claim when the intent is modification rather than deletion.

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