Skip to main content
Glama

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

Client-ops playbook catalog

get_client_ops_catalog
Read-only

Client-ops playbook catalog. The searchable index of the Ni Biashara client-ops playbook library: invoicing, POS daily operations, Google Business Profile upkeep and Texas local compliance — titles, categories, business types, triggers, jurisdictions, versions and review cadences. The discovery shelf for the playbook family. $0.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

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_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNofree text over title, summary and category (optional)
categoryNoplaybook category, e.g. money-ops, presence-ops, compliance-ops (optional)
jurisdictionNojurisdiction on the record, e.g. US-TX (optional)
business_typeNobusiness type on the record, e.g. restaurant (optional)

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?

Annotations only declare readOnly/openWorld/non-destructive; the description adds substantial behavioral context beyond them: the $0.1 USDC on Base price, the free-to-call-but-pay-on-delivery split, and the concrete x402 handshake (402 → PAYMENT-SIGNATURE → delivery). It also discloses the record fields returned (titles, categories, business types, triggers, jurisdictions, versions, review cadences), which is the kind of return-shape information annotations never carry.

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?

Purpose is front-loaded and the payment mechanics, which materially change how an agent must act, are stated plainly. The opening sentence "Client-ops playbook catalog" duplicates the title and is immediately restated, a minor waste; the long middle enumeration is dense but earns its place by defining scope.

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?

With no output schema and no annotations about payment, the description correctly supplies the return-field list, the $0.1 USDC cost, and the x402 402 → signature → delivery flow an agent must implement. It stops short of saying whether pagination exists or how many results come back per record set, a small residual gap for a search tool.

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?

Schema description coverage is 100%, so every parameter (q, category, jurisdiction, business_type) already has its own description with examples. The description adds only the framing that a free-text/taxonomic search is possible and that categories and jurisdictions exist on records, which the schema already shows. Baseline 3 applies when the schema does the heavy lifting.

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 searchable index of the Ni Biashara client-ops playbook library" plus "The discovery shelf for the playbook family" states a specific resource and search role, and the domain enumeration (invoicing, POS, GBP upkeep, Texas compliance) makes the scope concrete. It implicitly distinguishes itself from the retrieval siblings (get_client_ops_playbook and variants) by framing itself as the discovery layer, though it never names them.

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?

"The discovery shelf for the playbook family" implies you come here first to locate a playbook before fetching it, and the four filters imply narrowing-down usage. There is no explicit "use this when..." clause, no exclusion of the sibling get_client_ops_playbook / _plus / _localized tools, and no note on whether filters combine or which is best for a known title.

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