Skip to main content
Glama
Sign In
Steward MCP

Steward MCP

by brianbooms
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

steward_product

Fetch full details for a single catalog item—description, USD price, delivery method, and buy URL—after a catalog lookup; free and read-only. Then follow purchase steps for a live x402 quote.

Instructions

Full details for one catalog product: description, USD price, delivery method, and buy URL. Use after steward_catalog to zoom in on a single sku; when ready to pay, call steward_purchase_instructions for the live x402 quote. Free, read-only — never signs or spends.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sku": "<sku>"
    },
    "name": "steward_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
skuYesProduct sku exactly as returned by steward_catalog (e.g. 'data-affirmation').

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.6/5.0
Behavior4/5

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

No annotations, but the description states 'Free, read-only — never signs or spends', covering the safety profile. Adds the price field and delivery method context. Minor gap: no return-shape or error behavior beyond field list.

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?

Three compact sentences: purpose, sequence guidance, safety note — front-loaded with zero waste.

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?

Complete enough for an agent: purpose, sequencing, and safety are covered. No output schema, so field enumeration is helpful. A 4 rather than 5 because return format details (e.g., error on unknown sku) are undefined.

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%, so baseline is 3. The description reinforces the sku requirement via 'after steward_catalog to zoom in on a single sku', tying the parameter to its source, which is modest added value.

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 ('Full details for one catalog product') and enumerates the fields returned, distinguishing it from steward_catalog (zoom in on a single sku). An agent can select it without opening the schema.

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?

Explicitly routes: use after steward_catalog to zoom in; when ready to pay, call steward_purchase_instructions. Names the alternative and the transition condition.

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