Skip to main content
Glama

HeyIdentity

set_standard_claims

Sets which of the profile's generated standard claims are enabled (see get_configuration's standard_claims.available).

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

Input Schema

NameRequiredDescriptionDefault
enabledYesThe standard claims to enable, e.g. ["auth_time", "jti"]. Required. PUT .../claims/standard replaces the whole list: send the current list (GET /agent/v1/configurations/{configuration_id}) plus the new claim.
configuration_idYesThe configuration id (from create_tenant or get_tenant).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits, but it only says 'sets'. It omits critical details like the PUT operation replacing the entire list, permission requirements, and reversibility, although the schema's enabled parameter description does mention the replacement behavior.

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?

It is a single, front-loaded sentence with no wasted words. However, the extreme brevity leaves out useful structure like a usage note or warning about full replacement.

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 is minimal. It relies on the schema and an external reference for crucial behavior (full replacement) and does not itself convey enough for safe invocation.

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 coverage is 100%, so the schema already documents both parameters thoroughly, including that enabled is required and that PUT replaces the whole list. The description adds no additional parameter meaning beyond the schema baseline.

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: it sets which of the profile's generated standard claims are enabled. It distinguishes itself from custom-claim siblings by focusing on 'standard claims,' though it does not explicitly name alternatives.

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?

The only usage guidance is a pointer to get_configuration's standard_claims.available for discovering available claims. It does not explain when to use this tool versus edit_settings or add_custom_claim, nor does it state prerequisites or exclusions.

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