Skip to main content
Glama
Sign In

LabelTruth

by com.labeltruth
OverviewDiscussionsAdmin

List chemical forms of an element

list_forms
Read-onlyIdempotent

Chemical forms of one element that have at least one priced product in the region, in alphabetical order. No prices: forms are not ranked against each other.

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>"
    },
    "name": "list_forms"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world and non-destructive, so the safety bar is low. The description adds real scope information beyond them: results are filtered to forms that have at least one priced product in the region, returned alphabetically, and deliberately unranked by price.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with zero filler; the inclusion criterion and ordering are front-loaded, and the 'No prices' caveat is a compact, useful expectation-setter rather than padding.

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 two-parameter, fully documented, read-only list tool with rich annotations and no output schema, the description covers what qualifies for inclusion, ordering, and what is not returned (price ranking). Nothing an agent needs to call 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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning to region by explaining that it determines which forms qualify (forms priced in that region), not just where shipping stores are. It adds little on element beyond the schema's existing pointer to list_elements.

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?

States a specific verb+resource: chemical forms of a single element, with an explicit filter (at least one priced product in the region) and ordering (alphabetical). The resource is clearly distinct from list_elements (elements) and get_product, though it does not name those siblings explicitly.

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: the schema's element description points at list_elements for the slug, and 'No prices: forms are not ranked against each other' implicitly steers price-seeking agents elsewhere (e.g. cheapest_in_form). No explicit when-to-use/when-not or named alternative.

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