Skip to main content
Glama

HeyIdentity

edit_settings

Edits the settings; fields left out keep their value. settings: { profile?, b2c_policy_claim? (tfp or acr), validate_client_secrets?, token_lifetime_minutes?, token_shape?: { scope_claim_name?, scope_claim_format?, roles_claim_name?, roles_nested_key?, access_token_audience? } }.

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

Input Schema

NameRequiredDescriptionDefault
settingsYesThe settings to change. The configuration's settings. Fields left out keep their value.
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?

With no annotations, the description carries the full disclosure burden and does deliver the most important trait: omitted fields are preserved, i.e. this is a non-destructive partial merge rather than a replace. It also flags the Generic-profile-only scope of token_shape. It does not disclose permissions/validation failure behavior, whether token issuance is affected, or whether any change is irreversible.

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 partial-update rule is front-loaded and worth keeping, but the second sentence dumps the entire nested settings shape, duplicating a schema that is already fully described. The parenthetical "(tfp or acr)" and the token_shape expansion add length without adding information beyond the schema.

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, fully documented schema with no output schema, the description covers the essential mutation semantics (merge, not replace). It stops short of explaining what the call returns or what the agent should do after a successful edit, which matters because there is no output schema to describe the result.

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

Parameters4/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 every parameter and nested field; the description therefore only needs to add framing, which it does via the partial-update rule for the settings object. The inline field listing largely restates the schema, so this is close to baseline with a small value add.

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 the settings") and enumerates the mutable settings fields, so an agent can tell this is a partial update of a configuration's settings rather than a client/claim/user edit. It never explicitly says what a "setting" belongs to (a configuration) or names a sibling to contrast with, so differentiation is only implied by the field list.

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?

Usage is implied: this is the tool for changing an existing configuration's settings, and "fields left out keep their value" tells the agent to send only what changes. There is no explicit guidance on when to use create_configuration vs. this, no prerequisites (the configuration_id source appears only in the schema), and no note on whether profile switches interact with other edits.

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