token-of-esteem

create_gift

Place the order: write, print, and mail the booklet. CHARGES the buyer. The recipient is whoever you name in recipient, which may be your own user. Idempotent on idempotency_key for 24 hours. Pass shared_payment_token to pay tokenlessly, or omit it to charge the account's saved card.

Input Schema

TableJSON Schema

Name	Required	Description
`brief`	Yes	Structured brief about the recipient: what to celebrate, what to tease gently, and the inside jokes worth knowing.
`format`	No	Booklet format. Only manual_v1, a 16-page booklet, is supported today.
`recipient`	Yes	Who receives the booklet and where to mail it. Pass an inline recipient with a US ship_to, or a saved recipient_id.
`agent_note`	No	Optional note from the agent, stored with the order for support. Never printed in the booklet.
`idempotency_key`	Yes	Caller-chosen key that makes this order idempotent for 24 hours. Reuse the same key to retry safely without charging twice.
`preview_before_print`	No	If true, the gift pauses for buyer review before printing instead of printing automatically.
`shared_payment_token`	No	Single-use Stripe Shared Payment Token (spt_...) to pay without a stored card. Omit to charge the account default.

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description bears full burden. It discloses charging behavior, idempotency with a 24-hour window, and payment options (shared_payment_token vs stored card). However, it does not mention authentication needs, rate limits, or error states.

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?

Two sentences front-load the core action and charging, then cover idempotency and payment. No wasted words; every sentence adds value.

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

Completeness3/5

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

For a complex tool (7 params, nested objects) with no output schema, the description lacks return value details and prerequisite info (e.g., need validates_brief first?). It mentions payment but not error conditions. Adequate but not complete.

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 coverage is 100% (baseline 3). The description adds value beyond schema by clarifying the brief's purpose, recipient options (inline vs saved), and payment token pattern. It also notes that agent_note is never printed.

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 clearly states the verb ('Place the order') and the resource ('booklet'), and distinguishes from siblings like cancel_gift or get_gift by specifying the complete action of writing, printing, mailing, and charging.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when creating a gift order, but does not explicitly state when to use or not use this tool, nor does it mention alternatives or prerequisites among sibling tools.

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

All token-of-esteem 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.2/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: gift lifecycle (create, get, cancel, list), account info, pricing, resource listings, and brief validation. No overlap or ambiguity.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case (e.g., create_gift, list_voices, validate_brief), making it predictable for agents.

Tool Count5/5

12 tools is well-scoped for a gift ordering service, covering creation, retrieval, cancellation, pricing, account management, and resource listings without bloat.

Completeness5/5

The tool surface covers the full gift lifecycle and supporting operations (pricing, validation, account info, payment setup), with no obvious gaps for the intended domain.

Resources

Need Help?