Skip to main content
Glama

provider_regenerate_oidc_relying_party_secret

Regenerate an OIDC relying party's client secret by ID to rotate credentials after compromise or expiration.

Instructions

Regenerate the client secret of an OIDC relying party. Regenerates the client secret of an OIDC relying party. POST /cloudapi/1.0.0/openIdProvider/relyingParties/{id}/regenerateSecret

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": {
      "id": "<id>"
    },
    "name": "provider_regenerate_oidc_relying_party_secret"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesOIDC relying party's ID (path)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations declare non-read-only, non-idempotent, non-destructive, open-world behavior. The description adds no behavioral context beyond the operation: it does not say the previous secret stops working immediately, whether the new secret is returned once, or what permissions are required. It is consistent with the annotations but contributes nothing.

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 first two sentences are near-identical restatements ('Regenerate...' vs 'Regenerates...'), so one is redundant. It is short and front-loaded, but the duplication and raw POST path are not fully earning their place.

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 security-sensitive mutation with no output schema, the description should disclose consequences such as old secret invalidation and one-time secret return. It only names the operation and endpoint, leaving the agent without the context needed to call it safely.

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%, and the sole 'id' parameter is documented as the relying party's path ID. The description does not explain the ID format or source, so it adds no meaning beyond the schema; 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?

The description states a specific verb and resource: regenerate the client secret of an OIDC relying party. It distinguishes this operation from siblings such as provider_get_oidc_relying_party or provider_update_oidc_relying_party through the 'secret' and 'regenerate' terms, but it never explicitly contrasts them or states scope. Clear, but no sibling differentiation.

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 statement of when to use this versus update/delete/register, no prerequisites such as admin role, and no warning that the old secret becomes invalid. The only implied usage is the action itself, which is tautological.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools