Skip to main content
Glama

Ni Biashara Shelves — Africa FX, freight & compliance checks (x402)

Client-ops playbook plus — templates + review pack (premium)

get_client_ops_playbook_plus
Read-only

Client-ops playbook plus — templates + review pack (premium). Premium: the complete playbook plus its templates as standalone deliverables and the review pack (checks + done checklist) separated for direct execution. The v1 records do not yet carry the filled worked example; the payload names that gap rather than padding it. $1 USDC on Base. Returns the x402 URL to GET (402 → PAYMENT-SIGNATURE → delivery). Free to call this tool; payment happens on the URL.

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": {
      "playbook_id": "<playbook_id>"
    },
    "name": "get_client_ops_playbook_plus"
  }
}

Input Schema

NameRequiredDescriptionDefault
playbook_idYesplaybook id from client-ops-catalog (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses the cost ($1 USDC on Base), the full x402 handshake (402 → PAYMENT-SIGNATURE → delivery), the fact that invocation itself is free, and an honest data-quality caveat that v1 records lack the worked example. That is exactly the kind of behavior an agent cannot learn from annotations or schema.

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, then premium scope, caveat, price, and delivery mechanism in a logical order. Minor waste in restating the title verbatim at the start and in the slight overlap between '$1 USDC on Base' and 'payment happens on the URL', but no sentence is 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 one-parameter tool with no output schema, the description covers what is returned (an x402 URL to GET), the payment flow, and the known content gap. The only missing piece is explicit routing guidance against sibling playbook tools, which the payment and scope details largely compensate for.

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?

There is one parameter with 100% schema description coverage, and the schema already says it is the playbook id from client-ops-catalog. The description adds no format, sourcing, or validation detail beyond that, so baseline 3 applies.

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?

The description names a specific resource (the client-ops playbook) and states exactly what the premium tier adds: templates as standalone deliverables plus a separated review pack (checks + done checklist). This is distinguishable from a base playbook fetch, though it never explicitly names get_client_ops_playbook or get_client_ops_bundle as the non-premium alternatives.

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?

Usage is implied rather than stated: 'premium' and 'separated for direct execution' suggest when to pick this over the base playbook, and the payment sentence clarifies you can call it for free to obtain the URL. But there is no explicit when-to-use/when-not rule and no named alternative for the non-premium or bundled case.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources