Skip to main content
Glama

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

Client-ops playbook, localized tier (premium)

get_client_ops_localized
Read-only

Client-ops playbook, localized tier (premium). Premium live tier: one playbook re-checked and localized at call time for a named jurisdiction, with a generated 12-month deadline calendar. On the current snapshot build the live re-check cannot complete, so the call serves the record with its facts as checked and their as-of — plus the calendar where the record's own stated rules determine it — and names the degradation. $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>",
      "jurisdiction": "<jurisdiction>"
    },
    "name": "get_client_ops_localized"
  }
}

Input Schema

NameRequiredDescriptionDefault
playbook_idYesplaybook id from client-ops-catalog (required)
jurisdictionYesjurisdiction to localize for, e.g. US-TX (required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare readOnly/openWorld/non-destructive, and the description goes well beyond them: it discloses the $5 USDC on Base price, that the tool call itself is free and payment happens on the returned URL, the 402 → PAYMENT-SIGNATURE → delivery flow, and — crucially — that on the current snapshot build the live re-check cannot complete and the response degrades to as-of facts plus a conditional calendar while naming the degradation. That is unusually rich behavioral disclosure for a read tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and degradation caveat are front-loaded, and most sentences carry real information. However, the opening sentence restates the title verbatim and 'Premium live tier' repeats 'localized tier (premium)', and the remaining sentences are long and packed, so there is avoidable duplication and density.

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, the description must explain what comes back, and it does: the x402 URL to GET and the downstream payment handshake, plus the degraded-snapshot fallback. Given the tool's complexity (paid, degraded, jurisdiction-scoped), this is close to complete; only the exact shape of the delivered payload after payment is left unspecified.

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 coverage is 100% and both parameters are documented in the schema (playbook_id from the catalog, jurisdiction format such as US-TX), so the schema does the heavy lifting. The description reinforces that localization is keyed to a named jurisdiction but adds no format or constraint detail beyond what the schema already states.

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 the specific resource (a client-ops playbook record) and the specific operation (localized at call time for a named jurisdiction, with a 12-month deadline calendar), so an agent knows exactly what it gets. It signals the premium/live tier but never contrasts itself with siblings like get_client_ops_playbook or get_client_ops_playbook_plus, leaving the tier distinction implicit.

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 by the tier framing: call this when you need a jurisdiction-localized playbook plus deadline calendar. There is no explicit when-to-use vs. when-not, no named alternative for the non-localized or non-premium case, and no stated prerequisite beyond needing a playbook_id from the catalog (which the schema already carries).

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