Skip to main content
Glama

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

Cuisine collection pack

get_cuisine_pack
Read-only

Cuisine collection pack. One cuisine's collection from the Ni Biashara recipes shelf as a linked set: every fully worked dish on the shelf for that cuisine, with pairings. Launch collections are small and named as such — the shelf grows through the daily depth pass and never pads a pack. $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": {
      "cuisine": "<cuisine>"
    },
    "name": "get_cuisine_pack"
  }
}

Input Schema

NameRequiredDescriptionDefault
cuisineYescuisine to collect, e.g. Kenyan (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 already declare readOnly/openWorld/non-destructive, so the description adds the payment model: a fixed $0.5 USDC on Base, the x402 GET flow (402 → PAYMENT-SIGNATURE → delivery), and the fact the tool call itself costs nothing. It also discloses a content caveat — launch packs are small and never padded — which sets expectations about completeness. Missing only failure/expiry behavior of the paid URL.

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-loads the core payload description, then pricing and invocation mechanics. Most sentences earn their place, though phrases like 'named as such' and 'never pads a pack' lean promotional rather than informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 does describe the return shape (a linked set of dishes with pairings) and the operational return value (an x402 URL). However it leaves the delivered payload's structure and error cases unspecified, which matters for a paid retrieval 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 coverage is 100% for the single cuisine parameter, including an example, so the schema carries the load. The description restates 'one cuisine's collection' but adds no format, casing, or validity rules beyond what the schema already says.

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 specific verb+resource: it returns one cuisine's collection from the Ni Biashara recipes shelf as a linked set of fully worked dishes with pairings. An agent can tell what it gets without opening the schema. It stops short of naming how it differs from a near-sibling like get_recipe_collection_dossier, so it does not fully earn a 5.

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: it says which shelf and cuisine to pull from, and clarifies that calling the tool is free while payment happens on the returned URL. There is no explicit when-to-use vs when-not guidance and no comparison to the dossier-style siblings that presumably overlap.

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