Steward MCP

Overview Schema Source Related Servers Discussions Admin

steward_catalog

List all 29 products Brian Booms sells—ambient music, ringtones, wallpapers, track leases, game licenses, commissions—with SKU, name, and USD price to start a purchase flow.

Instructions

List everything buyable from Brian Booms — 29 products: ambient music, ringtones, wallpapers, track leases, game licenses, commissions. Returns sku, name, and USD price per product. Start any purchase flow here, then use steward_product for details on one item or steward_purchase_instructions for its live payment requirements. This lists WHAT Brian Booms sells; for the merchant directory (who sells) see steward_directory. Free, read-only — never signs or spends.

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_catalog"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.1Oct 17, 2026

TDQS

A4.7/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden and does so well: 'Free, read-only — never signs or spends' discloses the safety profile and that it is non-mutating, and 'never signs or spends' preempts a payment-flow misconception. It doesn't cover pagination or caching, but for a small static catalog that is minor.

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?

Front-loaded with the purpose and scope, followed by next-step routing, sibling disambiguation, and the safety note in that priority order. Every clause earns its place with no filler.

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

Completeness5/5

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

No output schema exists, but the description names the returned fields, the result count, and the follow-on tools, so an agent has everything needed to call and chain it. Nothing material is missing for a zero-parameter read-only catalog tool.

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?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to clarify or compensate for. It also helpfully documents the return shape (sku, name, USD price) in place of a schema.

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 ('List everything buyable from Brian Booms'), quantifies scope (29 products), and enumerates the catalog categories. It explicitly contrasts itself with the sibling steward_directory ('for the merchant directory (who sells)'), so an agent can distinguish the two 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 an explicit entry-point instruction ('Start any purchase flow here') plus the exact follow-up routing: steward_product for one item, steward_purchase_instructions for live payment terms. It also names when NOT to use this tool, directing merchant-directory lookups to steward_directory.

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