Skip to main content
Glama
Sign In

Ankra

by ai.ankra
OverviewDiscussionsAdmin

Rotate registry robot secret

rotate_registry_robot_secret
Destructive

Give a registry robot a new secret (the twin of ankra registry robots rotate). The managed credential holding its login is updated; anything that logs in with the old secret outside Ankra stops working. Robots Ankra manages are refused. The secret is never shown here. Requires credentials.write.

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": {
      "robot_name": "<robot_name>"
    },
    "name": "rotate_registry_robot_secret"
  }
}

Input Schema

NameRequiredDescriptionDefault
robot_nameYesThe robot's name, from list_registry_robots.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already flag destructive and non-idempotent, and the description adds real context beyond them: the old secret stops working outside Ankra, Ankra-managed robots are refused, and the new secret is never returned here. That is exactly the operational consequence an agent needs before a destructive rotation.

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

Conciseness5/5

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

Four short sentences, front-loaded with the action, then consequences, then the refusal case, then the auth requirement. Nothing is redundant and each sentence carries distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter destructive rotation with no output schema, the description covers the action, the blast radius, the failure mode, the permission requirement, and what is not returned. There is no material gap for an agent deciding whether to call it.

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 single parameter already documents its own source ("from list_registry_robots"). The description adds no additional meaning about robot_name, so the baseline of 3 applies.

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: giving a named registry robot a new secret, and identifies the CLI equivalent (`ankra registry robots rotate`). It is clearly distinguishable from generic secret tools by resource scope, but it never names the closest ambiguous sibling (`rotate_secret`) to disambiguate explicitly.

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 prerequisite ("Requires credentials.write") and an explicit exclusion ("Robots Ankra manages are refused"), which tells the agent when the call will fail. It stops short of stating the positive condition for choosing this over `rotate_secret` or `create_registry_robot`.

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

All Ankra toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources