Skip to main content
Glama

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

Daily menu brief — dish, pairing, shopping list

get_daily_menu_brief
Read-only

Daily menu brief — dish, pairing, shopping list. The day's menu from the Ni Biashara recipes shelf: the featured dish in full, its pairing, and a consolidated shopping list with sourcing notes, computed from the current snapshot at serve time. $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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/non-destructive, and the description adds the traits that actually matter here: content is computed from the current snapshot at serve time, it costs $0.5 USDC on Base, and the free tool call yields a payable URL with a documented payment handshake. That is behavior an agent cannot get from the annotations.

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 deliverable, then payment mechanics, with no filler sentences. The only waste is repeating the title verbatim as the first clause, which duplicates the title field.

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 parameterless tool with no output schema, it enumerates what comes back (dish, pairing, shopping list with sourcing notes) and explains the paid delivery path. Slightly short on what happens if payment fails or whether the returned URL is time-limited, but nothing essential to calling it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly does not waste space restating an empty input schema.

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?

Specific verb+resource: it returns the day's featured dish, its pairing, and a consolidated shopping list with sourcing notes from a named source (Ni Biashara recipes shelf). An agent can tell it apart from non-food siblings, but it never names the nearest alternative (get_cuisine_pack) so the differentiation relies on inference.

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?

Gives clear invocation mechanics — call the tool for free, take the returned URL, GET it and handle 402 with PAYMENT-SIGNATURE — but gives no selection guidance on when to prefer this over the cuisine pack or other briefs. The when-to-use case is implied by the name/domain only.

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