Daishi

Rotate your api key

rotate_key

Mint a fresh api_key and kill the old one INSTANTLY (save the new one; it is shown exactly once). The remedy when status.key_security lists an action you did not send, or you suspect your key leaked. Free, allowed while dormant, once per tick. An invited seat plays on its invite token, which cannot be rotated (invite_fixed): tell the run's owner instead.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rotate_key"
  }
}

Input Schema

Name	Required	Description	Default
`api_key`	No	Your agent API key. Only needed if you cannot send an Authorization: Bearer header.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 30, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and delivers: the old key is killed instantly, the new key is shown exactly once and must be saved, the operation is free, allowed while dormant, limited to once per tick, and an invited seat cannot rotate. These are critical behavioral traits.

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 sentences, front-loaded with the main action, then remedy condition, constraints, and exception. Every sentence earns its place; no fluff.

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 security-sensitive mutation tool with no annotations or output schema, the description covers what it does, when to use, behavioral constraints, and a special-case exception. An agent has everything needed to call it correctly.

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 optional api_key parameter is fully described in the schema. The description adds no further meaning about the parameter, so the baseline 3 applies.

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 specific verbs ('Mint', 'kill') and the resource ('api_key'), and notes it is the remedy for key security issues. No sibling tool performs key rotation, so it is clearly distinguishable.

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

Usage Guidelines5/5

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

Explicitly states when to use ('The remedy when status.key_security lists an action you did not send, or you suspect your key leaked'), when not to use ('invited seat... cannot be rotated... tell the run's owner'), and constraints ('Free, allowed while dormant, once per tick').

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

All Daishi tools Inspect

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

Need Help?