Skip to main content
Glama
Sign In
Steward MCP

Steward MCP

by brianbooms
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

steward_wiki

Fetch a concise Wikipedia article summary for quick research context; pass the article title as-is to support agent fact lookup.

Instructions

Concise summary of a Wikipedia article — quick research context for agents. Pass the article title as-is; the rail resolves it. For buying Brian Booms products use steward_catalog, not this tool. 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

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": {
      "topic": "<topic>"
    },
    "name": "steward_wiki"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesWikipedia article title, 1-200 chars (e.g. 'Mona Lisa').

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?

With no annotations, the description carries the full burden and does so well: it discloses the paid nature ($0.01 USDC on Base per call), the 402 quote flow, verification checks (scheme, network, token, payee), spend-cap refusal behavior, and the security guarantee that the payer key never leaves the machine. It stops short of stating the return format or confirming the operation is non-destructive.

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 the purpose before payment details, and most sentences earn their place given this is a paid tool. The payment paragraph is dense but relevant; the product-vs-catalog aside is slightly tangential yet functional as disambiguation.

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-param tool with no output schema and no annotations, the description covers purpose, parameter handling, cost, and payment mechanics thoroughly. The main remaining gap is that it never sketches the shape of the returned summary.

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% for the single 'topic' parameter, so the baseline is 3. The description adds value beyond the schema by instructing 'Pass the article title as-is; the rail resolves it,' clarifying that no normalization or disambiguation is expected from the caller.

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 and resource — 'Concise summary of a Wikipedia article' — and frames the scope ('quick research context for agents'). It also explicitly distinguishes itself from one sibling (steward_catalog for buying Brian Booms products), so an agent can route correctly 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear context ('quick research context for agents') and names a specific alternative with its own domain (steward_catalog for product purchases). It does not cover when-not-to-use relative to the other research-adjacent siblings, but the primary routing guidance is present.

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