Skip to main content
Glama

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

One complete client-ops playbook

get_client_ops_playbook
Read-only

One complete client-ops playbook. One complete playbook from the Ni Biashara client-ops library at its current version: executable steps with decision points, failure modes with fixes, objective pass/fail checks, fill-in templates and a done checklist. Every drifting fact carries its source and as-of inside the record. $0.5 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"
  }
}

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?

With readOnly/openWorld annotations already set, the description still adds substantial behavior: a $0.5 USDC cost on Base, the x402 flow (402 → PAYMENT-SIGNATURE → delivery), and the explicit clarification that calling the tool is free and payment occurs on the returned URL. It also states that volatile facts carry source and as-of metadata, which tells the agent how to judge freshness. This is consistent with readOnlyHint=true since no mutation occurs on the tool call itself.

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 content is dense and front-loaded with purpose, then contents, price, and delivery flow in a logical order. The opening clause 'One complete client-ops playbook. One complete playbook…' duplicates the title and then immediately repeats itself, which is the only real waste in an otherwise tight description.

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-parameter read tool with no output schema, the description covers what an agent needs: what is returned, that it is a paid x402 resource, and how payment is completed. The only ambiguity is what the GET actually delivers (raw JSON vs. rendered document), and how large or paginated the payload is, which is left unstated.

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?

One parameter at 100% schema coverage, so the baseline is 3. The description adds only the provenance pointer ('from client-ops-catalog') already present in the schema field description; it contributes no format or validity detail beyond that.

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 goes beyond the title: it states this returns exactly one playbook from the Ni Biashara client-ops library at its current version, and enumerates the contents (steps, failure modes, pass/fail checks, templates, checklist). That is a specific resource with a defined scope. It does not explicitly contrast against the sibling get_client_ops_playbook_plus, which one might reasonably confuse it with.

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 only implied: the parameter description says the id comes from client-ops-catalog, which nudges the agent to call the catalog first. There is no explicit 'use this when…' guidance and no statement of when to prefer the _plus or _bundle siblings. Adequate but leaves the routing decision to inference.

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