Skip to main content
Glama

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

Client-ops playbook bundle (premium)

get_client_ops_bundle
Read-only

Client-ops playbook bundle (premium). Premium: a full category of the Ni Biashara client-ops library for one business type (e.g. all money-ops playbooks), or the complete starter set of playbooks when no filter is given. Full records, current versions. $2.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

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": "get_client_ops_bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoplaybook category to bundle, e.g. money-ops (optional)
business_typeNobusiness type to bundle for, e.g. restaurant (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnly/openWorld/non-destructive, but the description adds substantial behavior the agent could not otherwise know: a $2.5 USDC cost on Base, that the tool call itself is free, and that it returns an x402 URL with a 402 → PAYMENT-SIGNATURE → delivery handshake. That payment flow is exactly the kind of non-obvious side effect worth disclosing, though rate limits and failure behavior on unpaid delivery are unstated.

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?

Dense and front-loaded: scope, tier, contents, price, and delivery mechanics arrive in order with no filler sentences. The opening repeats the title verbatim, which is mild waste, and the telegraphic phrasing ('402 → PAYMENT-SIGNATURE → delivery') is compact but requires prior x402 familiarity.

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 paid retrieval tool with no output schema, the description covers everything an agent needs to call it correctly and anticipate the payment step. The remaining gap is sibling routing — it does not clarify why an agent would pick this bundle versus the single-playbook or catalog tools.

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 the baseline is 3, but the description earns extra by explaining the semantic consequence of the two optional params: supplying category/business_type yields that full category, omitting them yields the complete starter set. That effect-of-omission is real meaning beyond the schema's 'optional' labels.

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?

States a concrete verb+resource: bundles a full playbook category for one business type, or the complete starter set when no filter is given, with full records at current versions. The 'premium' qualifier hints at cheaper siblings (get_client_ops_playbook, get_client_ops_playbook_plus, get_client_ops_catalog) but none are named, so the differentiation is implied rather than explicit.

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?

Conveys the one branching rule that matters for invocation: with a filter you get a whole category, without a filter you get the starter set. It never says when to choose this bundle over the single-playbook or catalog siblings, so cross-tool selection is left 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