Skip to main content
Glama
Sign In

LabelTruth

by com.labeltruth
OverviewDiscussionsAdmin

Cheapest products in one form

cheapest_in_form
Read-onlyIdempotent

Products of one chemical form ranked by euro per 1000 mg of the element, cheapest first, at the shop price when last checked. Only ranked products are listed (limit 1-10, default 5).

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": {
      "element": "<element>",
      "form": "<form>"
    },
    "name": "cheapest_in_form"
  }
}

Input Schema

NameRequiredDescriptionDefault
formYesForm slug from list_forms, e.g. "magnesium-glycinate" (^[a-z0-9-]{1,80}$).
limitNoHow many products, 1-10. Default 5.
regionNoShipping region: "GLOBAL" (stores that ship worldwide, default) or a two-letter country code, e.g. "DE".
elementYesElement slug from list_elements, e.g. "magnesium" (^[a-z0-9-]{1,80}$).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, idempotentHint=true, and destructiveHint=false, so safety and idempotency are covered. The description adds useful context beyond annotations: pricing basis in euro per 1000 mg of elemental content, shop price at last check, and that only ranked products are returned. It does not disclose result ordering edge cases, missing-price behavior, or pagination.

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?

A single sentence, front-loaded with the ranking metric and scope, with the limit constraint appended. It is efficient, though the limit restatement duplicates the schema and the sentence is dense.

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 read-only ranked-list tool with a fully documented four-parameter schema and no output schema, the description covers the ranking basis, pricing assumptions, and that only ranked products appear. It is nearly complete; the main gap is guidance on alternatives like get_product for individual lookups.

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%, with each of the four parameters documented including slug formats, the limit range of 1-10, and region semantics (GLOBAL default or two-letter country code). The description only restates the limit default and the ranking metric, adding little beyond the schema. Baseline 3 applies when schema coverage is high.

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 states a specific verb-and-resource combination: ranking products of one chemical form by euro per 1000 mg of the element, cheapest first. It also specifies the pricing basis (shop price when last checked) and the limit range. It does not name or distinguish itself from siblings like get_product, though its ranking focus is distinct enough to infer.

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 implied rather than stated: an agent can infer this tool is for comparing prices within a single form, and the requirement for element and form slugs from list_elements and list_forms is conveyed via the schema. There is no explicit when-not or alternative routing (e.g., use get_product for a single product's details), leaving the agent to infer selection.

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

All LabelTruth 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