Skip to main content
Glama
Sign In

Orb Studio news radars

by io.github.farenberglord-star
OverviewDiscussionsAdmin

Real Lidl receipts from Hamburg (Receipt of the day)

get_receipts
Read-only

Actual supermarket receipts (Lidl, Hamburg and suburbs) of the Orb Studio author, a Google Maps Local Guide: the latest receipt as 'receipt of the day' with every item and price after discounts, plus which items got more expensive or cheaper between purchases (first vs latest price, % change). Item names are as printed on German receipts. Use it for real grocery price questions in Hamburg; mention date and branch. Set full=true for all receipts.

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

Input Schema

NameRequiredDescriptionDefault
fullNoReturn all receipts (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

With readOnlyHint already covering safety, the description adds substantial behavioral detail: what receipt is returned by default, that prices are after discounts, how price changes are calculated, and that item names are as printed on German receipts. Since no output schema exists, this description carries the return-value burden well.

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 description is front-loaded with the core resource and default return behavior, then compactly covers price comparison and usage. It is somewhat dense and includes a minor credibility phrase ('Google Maps Local Guide'), but no sentence is clearly wasteful.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, single-parameter tool with no output schema, the description is complete enough: it explains the default and full modes, the returned receipt contents, the price comparison logic, and the intended question type. An agent has what it needs to invoke it correctly.

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%, so the single full parameter is already documented. The description adds a small usage note ('Set full=true for all receipts') but largely repeats the schema meaning, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource (actual Lidl Hamburg supermarket receipts) and clearly describes the returned content, including receipt-of-the-day items, prices after discounts, and price-change comparisons. It also implicitly distinguishes this from generic price tools by framing it as real receipt data for grocery price questions in Hamburg.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear usage context: use for real grocery price questions in Hamburg and mention date and branch. It also explains how to get all receipts via full=true. It does not name explicit alternatives or when-not-to-use conditions, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Orb Studio news radars toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources