Relaystation

create_baton

Create a baton — a prepaid storage object. Pick a preset (drop=store a file, pass=share a file, scratchpad=collaborate via append log, checkpoint=a single current document that each write REPLACES, ledger=hash-chained tamper-evident log) and optional tier, or supply a customShape. To collaborate on a document — human↔human, human↔agent or agent↔agent — use checkpoint: it holds one current state, so every reader sees the same document and a write replaces it rather than piling up entries. scratchpad is an append log: good for a running buffer two agents both add to, but readers of a scratchpad see the newest entry only. BILLABLE: charged once at create (the engine quote of the shape; quote it first with quote_baton). Funded from your balance via your rs_live_* key. Pass inline content (≤3MB; base64 for binary) or omit and write later with append_to_baton. flags.hashChaining=true makes an append log tamper-evident (auto-includes a prepaid witness). NOTE: hash-chained batons (ledger preset, or flags.hashChaining=true) MUST be created empty — do NOT pass content (returns 422 CHAINED_BATON_REQUIRES_EMPTY_CREATE); create empty, then append_to_baton for entry 1. Example (store): create_baton {preset:"drop", tier:"femto", content:""}. Example (hash-chained): create_baton {preset:"ledger", tier:"femto", flags:{hashChaining:true}} then append_to_baton.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No
`tags`	No
`tier`	No	Bundle tier — valid tiers depend on preset (drop: femto/pico/nano/micro/standard/big · pass: femto/pico/nano · scratchpad: pico/nano/micro/standard/big · checkpoint: nano/micro/standard/big · ledger: femto/pico/nano/micro/standard/big). Plus 'custom' (with customShape) for any preset.
`flags`	No
`preset`	Yes
`content`	No
`contentType`	No
`customShape`	No
`description`	No
`contentEncoding`	No

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 full responsibility. It discloses billing (BILLABLE, charged once), funding via rs_live_* key, the 3MB content limit, base64 for binary, the hashChaining flag auto-including a prepaid witness, and the 422 CHAINED_BATON_REQUIRES_EMPTY_CREATE error condition.

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?

The description is lengthy but justifiably so for a multi-preset tool. It front-loads purpose and preset guidance and includes concrete examples. Some redundancy exists (checkpoint behavior described twice), and the prose is dense, but it remains organized and useful.

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?

It covers billing, content size, preset behavior, flags, and error cases, which is strong for 10 parameters with nested objects. However, with no output schema, it does not mention what the create response contains (e.g., baton ID), which would aid downstream tool chaining.

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

Parameters4/5

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

Schema description coverage is very low (10%, only tier has a description). The description compensates by explaining preset meanings, per-preset tier validity, content encoding, and flags.hashChaining semantics. It does not detail name/tags/customShape fields, but those are relatively self-explanatory, so the addition is substantial.

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 'Create a baton — a prepaid storage object', giving a clear verb and resource. It then enumerates five presets with distinct behaviors, which differentiates it from sibling tools like read_baton and append_to_baton.

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?

Provides explicit when-to-use guidance: recommends checkpoint for collaboration, distinguishes scratchpad as an append log, tells to quote first with quote_baton, and says to write later with append_to_baton. It also gives a critical exclusion: hash-chained batons must be created empty.

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

All Relaystation tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool targets a distinct action and resource, such as baton operations, agent messaging, contracts, and account management. There is no overlap in functionality, making it clear which tool to use for each task.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case (e.g., append_to_baton, create_baton, message_agent). The verbs are descriptive and uniform, aiding predictability.

Tool Count5/5

With 14 tools, the server covers its domain (agent coordination, batons, contracts, tool discovery) without being overbearing. The count is well-scoped for a platform offering a variety of operations.

Completeness3/5

The tool set covers core operations like creating, reading, and appending to batons, as well as messaging and contracts. However, it lacks list or delete operations for batons and contracts, which are notable gaps for a complete lifecycle.

Resources

Need Help?