Skip to main content
Glama
Sign In

Ankra

by ai.ankra
OverviewDiscussionsAdmin

Rename personal AI key

rename_personal_ai_key

Rename one of your own AI keys: only its label changes, never the key or its place in the order. key_id comes from list_personal_ai_keys. Only for the person themselves, in their own chat or over MCP with their own token: refused for a service account, an AI agent, a subworker and a dispatched or autonomous run.

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": {
      "key_id": "<key_id>",
      "label": "<label>"
    },
    "name": "rename_personal_ai_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelYesThe new name for the key, at most 100 characters; empty clears it.
key_idYesThe id of one of your AI keys, as list_personal_ai_keys shows it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare non-readOnly, non-destructive, non-idempotent, but the description adds substantive context the annotations cannot: that the mutation is label-only, that ordering and the key material are untouched, and that identity/permission gating applies. It stops short of describing failure behavior for an unknown or foreign key_id, so it is strong but not exhaustive.

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?

Two tight sentences with the scope-defining clause front-loaded and zero filler. The second sentence is dense (a four-item refusal list) but each element carries real routing value.

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

Completeness4/5

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

For a two-parameter, non-destructive mutation with a fully documented schema and no output schema, the definition covers scope, id provenance, and authorization. Only error/edge behavior for invalid key_ids is unaddressed, a minor gap.

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 both parameters are already documented, including the 100-character cap and empty-clears semantics for label. The description only adds the source tool for key_id, which the schema itself also notes, so it adds little beyond the structured data.

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 ('Rename one of your own AI keys') and immediately scopes the effect ('only its label changes, never the key or its place in the order'), which cleanly separates it from reorder_personal_ai_keys and delete_personal_ai_key.

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?

Gives the provenance rule for the id ('key_id comes from list_personal_ai_keys') and an explicit who-may-call rule, naming four caller classes that are refused (service account, AI agent, subworker, dispatched/autonomous run). That is concrete when-to-use and when-not-to-use guidance rather than inference.

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