Skip to main content
Glama

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

One complete recipe record

get_recipe
Read-only

One complete recipe record. One complete recipe record from the Ni Biashara recipes shelf: ingredients with quantities and units, timed steps, substitutions that work, sourcing notes and pairing. Query by record id or exact dish title. $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_recipe"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNorecipe record id, e.g. kenyan-beef-pilau (this or title required)
titleNodish title, exact or close match (this or id 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?

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint), and the description adds materially new behavior: a $0.1 USDC cost on Base, a two-step x402 handshake (402 → PAYMENT-SIGNATURE → delivery), and the important clarification that the tool call itself is free while payment happens on the returned URL. That is real value beyond structured fields, though it does not describe what happens if the payment is declined or the record is not found.

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?

The pricing and delivery mechanics are front-loaded after the purpose statement, and the sentences are dense with useful facts. The opening sentence 'One complete recipe record.' merely restates the title before the next sentence repeats the same phrase, which is wasted space.

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-parameter read-only lookup with no output schema, the description covers purpose, lookup keys, payload contents, and the payment/retrieval flow an agent must follow to actually get the record. The one gap is that required-parameters is 0 in the schema, yet the description never says a call with neither id nor title will fail.

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% and the schema already documents both 'id' and 'title' with the 'this or title required' constraint and the exact/close-match note. The description's 'record id or exact dish title' largely restates the schema, so 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 gives a specific verb and resource ('Query by record id or exact dish title') and enumerates the payload (ingredients with quantities and units, timed steps, substitutions, sourcing notes, pairing), so an agent knows exactly what it retrieves. It does not differentiate itself from plausible siblings such as get_recipe_collection_dossier or get_cuisine_pack, so it stops short of 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?

It states the two lookup keys and that either id or title selects a record, which is implied usage guidance for calling the tool. There is no explicit when-to-use versus the collection/cuisine-pack siblings and no when-not guidance, so usage is only partially addressed.

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