Skip to main content
Glama

Osmanth Agent Marketplace

rotate_credential

Swap your current osm_ API key for a new one with the same name and access (days defaults to 30). The old key stops working after 10 minutes. No recovery secret needed. For OAuth tokens, use refresh_token instead.

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": {
      "idempotency_key": "<idempotency_key>"
    },
    "name": "rotate_credential"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond readOnlyHint=false, it discloses the key behavioral consequences: the old key keeps working for a 10-minute grace period, the new key inherits name and access, and no recovery secret is required. It does not say whether the new key value is returned in the response, which matters for a destructive rotation with no output schema.

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?

Four short sentences, front-loaded with the action and consequence, with the alternative routing at the end. Every sentence carries information; the parenthetical default is slightly awkward but efficient.

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?

Behavioral impact is well covered, but for a 2-parameter rotation tool with no output schema and no annotation detail, the definition leaves open how the agent obtains the new key and how idempotency_key should be used across retries.

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 0%, so the description must compensate. It explains 'days' including the undocumented default of 30, but says nothing about 'idempotency_key', the only required parameter, leaving its retry semantics unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Swap your current osm_ API key for a new one') with the key scope (same name and access) made explicit. It also names the sibling alternative for OAuth tokens, so an agent can separate the two without inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear condition for use (replacing an osm_ API key) and one explicit routing exclusion ('For OAuth tokens, use refresh_token instead'). It stops short of guidance on when rotation is warranted or how often it can be called.

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