Skip to main content
Glama
Sign In
Steward MCP

Steward MCP

by brianbooms
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

steward_audio_rest

Play calm Brian Booms soundscapes for sleep, rest, and recovery; set an optional 1–120 minute length or use the default.

Instructions

Wind-down audio lane — calm Brian Booms soundscapes for rest and recovery. Choose this for sleep and relaxation; choose steward_audio_focus for deep work, or steward_audio_match when you want a track picked for a specific mood. Optional length in minutes (1-120); omit for the rail default. Paid: $0.01 USDC on Base per call — the rail quotes each call via 402; this server verifies the quote (exact scheme, Base network, USDC, Steward payee) and settles from your wallet automatically, refusing quotes over your per-call or daily spend caps. Your payer key never leaves your machine.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "steward_audio_rest"
  }
}

Input Schema

NameRequiredDescriptionDefault
minutesNoDesired wind-down length in minutes, 1-120. Omit for the rail default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does so well: it discloses the paid model ($0.01 USDC on Base), the 402 quote flow, verification criteria (scheme, network, token, payee), automatic settlement, spend-cap refusal behavior, and that the payer key stays local. It stops short of describing the return payload (e.g., what the audio lane actually returns) or error/repeat-call behavior.

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-loaded with purpose and routing guidance, then payment mechanics. It is a bit long, but every sentence covers material an agent needs given the absence of annotations and output schema.

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?

For a simple optional-param audio tool with no output schema and no annotations, the description covers selection, parameter default, and the full payment/verification lifecycle. Only the return-value shape is left unspecified, a minor gap given output schema 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?

The single parameter is already fully documented in the schema at 100% coverage (range 1-120, omission default). The description merely restates the same range and omit-default, adding no new semantics, so 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+resource and scope: a 'wind-down audio lane' of calm soundscapes for rest and recovery. It explicitly names the siblings it is NOT for (steward_audio_focus for deep work, steward_audio_match for mood-picked tracks), so an agent can disambiguate without opening schemas.

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?

Gives explicit when-to-use ('sleep and relaxation') plus the conditions that route to alternatives, naming both sibling tools. Nothing about tool selection is left to inference.

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

Deploy Server

Other Tools