Skip to main content
Glama
Sign In
Steward MCP

Steward MCP

by brianbooms
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

steward_joke

Generate a clean, family-friendly joke from Synthetic Universe; pass a session id to avoid repeats within that session, or omit it for a one-off.

Instructions

One clean, original, family-friendly joke from the Synthetic Universe — computed on the rail, no third-party upstream. Pass a session id to avoid repeats within a session; omit it for a one-off joke. 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_joke"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionNoOptional session id (up to 64 chars) — jokes will not repeat within the same session id.

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 zero annotations, the description carries the full burden and does so thoroughly: it discloses the cost ($0.01 USDC on Base), the 402 quoting/verification flow, exact scheme/network/payee checks, automatic settlement, spend-cap refusal behavior, and the guarantee that the payer key stays local. This is a rich, safety-relevant behavioral profile for a paid tool.

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 purpose is front-loaded ahead of the payment details, and every sentence is relevant for a paid tool. The payment clause is a long run-on, but its content (cost, network, caps) earns the space rather than padding.

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, and the full payment lifecycle an agent needs to invoke it correctly. Only the routing against sibling content tools 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?

Schema description coverage is 100% and the schema already explains the session id's repeat-avoidance semantics, which the description essentially restates. The only marginal addition is framing omission as a 'one-off' use case, which does not meaningfully exceed the schema.

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 ('One clean, original, family-friendly joke') and the source ('Synthetic Universe'), so an agent immediately knows this returns a joke. It does not, however, distinguish itself from adjacent content siblings like steward_fortune or steward_sleep_tip, leaving the choice to inference.

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?

Gives clear guidance on the optional parameter ('pass a session id to avoid repeats; omit it for a one-off joke'), which is genuinely useful context. But it never says when to pick this tool over sibling content tools (fortune, sleep_tip, wiki), so usage is only implied.

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