Skip to main content
Glama

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

Recipe collection dossier (premium)

get_recipe_collection_dossier
Read-only

Recipe collection dossier (premium). Premium dossier over a region or cuisine of the Ni Biashara recipes shelf: the full dish records plus per-dish sourcing notes and substitution chains, with the snapshot's actual coverage named. Built for menu planning; coverage is what the shelf really holds, never invented dishes. $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_recipe_collection_dossier"
  }
}

Input Schema

NameRequiredDescriptionDefault
regionNoregion text, e.g. Kenyan Coast (this or cuisine required)
cuisineNoexact cuisine, e.g. Kenyan (this or region required)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnly/openWorld annotations, the description discloses the trust-relevant behavior: coverage reflects 'what the shelf really holds, never invented dishes,' plus the full payment mechanic ($2.5 USDC on Base, free to call, 402 → PAYMENT-SIGNATURE → delivery on the returned x402 URL). What's missing is any note on dossier size/volume or failure behavior when a region yields thin coverage.

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 and coverage guarantee are front-loaded, and the payment sentence is placed last where an agent needs it before acting. The opening 'Recipe collection dossier (premium).' merely restates the title and is the one sentence that doesn't earn its place.

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 two-param, no-output-schema, paid tool, the description covers what is returned, the honesty guarantee on coverage, and the entire purchase flow — everything an agent needs to call and complete payment. It stops short of describing dossier scope limits (how many dishes, what happens with an unknown region), which would complete the picture.

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 properties already carry their own descriptions and the 'this or cuisine required' constraint, so the schema does the heavy lifting. The description adds only the light framing 'over a region or cuisine,' matching rather than extending the schema; baseline 3 applies.

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 a specific verb+resource beyond the title: a dossier over 'a region or cuisine of the Ni Biashara recipes shelf' containing 'the full dish records plus per-dish sourcing notes and substitution chains.' That is concrete enough to picture the payload, but it never names the sibling it supersedes (e.g. get_cuisine_pack or get_recipe), so differentiation rests on the word 'dossier' alone.

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 by 'Built for menu planning,' which gives a scenario but no when-not conditions and no named alternatives. An agent must infer from sibling names when to pick this over get_cuisine_pack or get_recipe; nothing in the text excludes or routes.

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