Rayana AI

rayana_ai_start_checkout

Read-only

Get a link your principal opens in a browser to subscribe. No API key needed. Give them the URL — you cannot complete this yourself, and should not try: they sign in, accept the Terms and authenticate the payment.

If the tier includes API access, their account page then shows a short
pairing code; read it back into ``rayana_ai_complete_setup`` to get your
API key without them pasting a secret into this conversation. **Standard
does not include API or MCP access** — if the point of the purchase is a
key for you, ask for pro or elite.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tier`	No		pro
`interval`	No		month

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`tier`	Yes
`interval`	Yes
`price_usd`	Yes
`next_steps`	Yes
`pairing_note`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 18, 2026

TDQS

A4.5/5.0

Behavior5/5

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

The description goes well beyond the readOnlyHint annotation, explaining the human-in-the-loop behavior: the principal signs in, accepts Terms, and authenticates payment. It also discloses the pairing-code flow and the critical limitation that Standard tier lacks API/MCP access, which is exactly the kind of behavioral context an agent needs.

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 primary purpose and then adds only high-value operational details: no API key needed, cannot complete checkout, pairing code flow, and tier caveat. Every sentence earns its place, and the structure moves naturally from what the tool does to how to use the result.

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?

Given the tool's human-in-the-loop nature and the presence of an output schema, the description covers everything needed to invoke it correctly: the link's purpose, the agent's limitations, the follow-up pairing-code flow, and tier restrictions. The reference to rayana_ai_complete_setup completes the end-to-end context.

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 description coverage is 0%, so the description must compensate. It adds meaningful tier semantics by warning that Standard does not include API or MCP access and recommending pro/elite for key-based use. However, it does not explain the interval parameter at all, though 'month' and 'year' are reasonably self-evident from the enum names.

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 opens with a specific verb and resource: 'Get a link your principal opens in a browser to subscribe.' It clearly distinguishes this tool from the sibling setup flow by naming rayana_ai_complete_setup as the follow-up, and it makes the tool's boundary explicit: the agent cannot complete the checkout itself.

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?

The description gives clear context for when this tool is appropriate: when a subscription link is needed and a human must authenticate. It provides an explicit exclusion ('you cannot complete this yourself, and should not try') and steers the user toward pro/elite if the goal is API access, though it does not name alternative tools for plan comparison.

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?