Skip to main content
Glama
Sign In
Steward MCP

Steward MCP

by brianbooms
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

steward_sleep_tip

Fetch a practical sleep-hygiene tip from a rotating set of 12. Omit the index for today's tip or pass 0-11 to choose a specific habit; no medical claims.

Instructions

One genuine sleep-hygiene tip from Brian Booms' rotating collection of 12 — practical habits, never medical claims. Omit the index for today's rotating tip; pass 0-11 for a specific one. 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_sleep_tip"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexNoTip index 0-11 for a specific tip; omit for today's rotating tip.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.9/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses the price ($0.01 USDC on Base), the 402 quote flow, that the server verifies scheme/network/token/payee, that it settles from the wallet automatically, that it refuses quotes exceeding per-call or daily caps, and that the payer key stays local. This is rich behavioral and safety context beyond any structured field.

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, then index behavior, then payment details — a sensible ordering. The payment paragraph is long but earns its place given the absence of annotations and the tool's paid nature; no sentence is pure filler.

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 single-optional-param tool with no output schema and no annotations, the description covers purpose, parameter behavior, payment mechanics, and spend-cap safety. Return shape is not described, but the tool is trivially simple, so this is nearly complete.

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 100% and the schema already documents the index with the same omit-for-today wording and 0-11 bounds, so the description's restatement adds little. Baseline 3 is appropriate when the schema fully documents the single parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: it returns 'One genuine sleep-hygiene tip from Brian Booms' rotating collection of 12,' with a scoping note ('never medical claims'). It is clearly distinguishable from content siblings like steward_joke or steward_fortune by resource, though it does not name them explicitly.

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?

It explains the index mechanic (omit for today's rotating tip, pass 0-11 for a specific one), which is a usage instruction, but offers no guidance on when to prefer this over other steward_* content tools or any exclusions. Usage is implied by the resource name rather than stated.

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