Rayana AI

rayana_ai_complete_setup

Destructive

Exchange a pairing code from your principal's account page for an API key. Ask them to confirm before you call this: it issues a new key and immediately invalidates the account's previous one, so any other client already using a key will stop working until it is given the new value.

The key comes back once and is not retrievable afterwards — only a hash of
it is stored. Put it in the ``X-API-Key`` header on this connection and on
any REST call. Codes are single-use, expire in 15 minutes, and are burnt
after a few wrong guesses; if one is refused, ask for a fresh one rather
than retrying.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`code`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	Yes
`tier`	Yes
`api_key`	Yes
`mcp_url`	Yes
`header_name`	Yes
`rest_base_url`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 18, 2026

TDQS

A5/5.0

Behavior5/5

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

The description goes well beyond the destructiveHint annotation by disclosing that the new key invalidates the old one, is shown only once, is only stored as a hash, and that codes are single-use, expire in 15 minutes, and burn after wrong guesses. These operational consequences are exactly what an agent needs to avoid causing harm.

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?

The description is front-loaded with the core action and then adds dense, high-value operational warnings. Every sentence earns its place; none are redundant with the schema or annotations.

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?

With one parameter, an output schema present, and annotations covering destructive behavior, the description provides all necessary context: what to do, what to warn about, how the key is used afterward, and failure handling. Nothing critical is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema only provides 'code' with no description and 0% parameter documentation coverage. The description compensates fully by explaining what the code is, where to obtain it, its single-use nature, expiry, and failure behavior.

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?

The description states a specific verb and resource: exchange a pairing code for an API key. It clearly identifies the source of the code (principal's account page) and the purpose, distinguishing it from the many sibling data tools.

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?

Explicit guidance is given on when to call and what to do before calling: confirm with the principal because the previous key is immediately invalidated. It also explains when not to retry a refused code and instructs the agent to request a fresh one, which is strong usage direction.

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

All Rayana AI 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?