Skip to main content
Glama
Sign In

Ankra

by ai.ankra
OverviewDiscussionsAdmin

Test personal AI key

test_personal_ai_key
Read-only

Check one of your own AI keys with its provider now and say what the provider answered: accepted (Ankra uses it again in its place in the order), refused (Ankra stops using it until a test passes), or out of credit (Ankra skips it until retry_after). Never returns the key; it records only the key's status. 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>"
    },
    "name": "test_personal_ai_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.4/5.0
Behavior5/5

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

Adds substantial context beyond the readOnlyHint annotation: the provider is contacted live, the result changes Ankra's key ordering/eligibility ('uses it again in its place in the order', 'stops using it', 'skips it until retry_after'), and the key material is never returned. The authorisation preconditions are spelled out, which is exactly the behaviour an agent needs before calling it.

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?

Front-loads the action and outcomes, and every clause carries information (outcomes, key non-disclosure, eligibility). The final eligibility clause is a long run-on list that could be tightened, keeping it just short of a 5.

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 tool with no output schema, the description supplies the missing return semantics by naming the three possible statuses and their downstream effects, plus the side-effect (status recorded, key never exposed). Nothing needed to call it correctly is absent.

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 key_id parameter is already documented with a pointer to list_personal_ai_keys. The description only reinforces the ownership constraint ('one of your own AI keys') without adding format or validation detail, so the schema does the heavy lifting and 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 a specific verb and resource ('Check one of your own AI keys with its provider now') and immediately enumerates the three outcomes it can return. It is clearly distinct from the sibling key-management tools (list_personal_ai_keys, rename_personal_ai_key, delete_personal_ai_key) because it is the only one that performs a live provider probe.

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 explicit eligibility and exclusions: only for the person themselves, in their own chat or over MCP with their own token, and refused for a service account, AI agent, subworker, or dispatched/autonomous run. It does not explicitly route the agent to alternatives (e.g. list_personal_ai_keys to discover key_id), but the when-to-use context is clear.

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