Skip to main content
Glama

stone_sheet

Crystal sheet: description, origin, themes, uses, care, affirmation and linked chakras. Price: $0.005 USDC per call (x402).

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": {
      "id": "<id>"
    },
    "name": "stone_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesStone id from /v1/stones
langNoLanguage of the core texts (default it)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden, yet it does usefully disclose the pay-per-call model and exact price ($0.005 USDC via x402), which is real behavioral context an agent needs before invoking. It omits everything else: that this is a read-only retrieval, what happens with an unknown id, and whether the returned texts are charged per language variant.

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?

Two short sentences with no filler, and the content summary is front-loaded before the pricing note. The leading label 'Crystal sheet:' is mildly redundant with the tool name, but nothing else wastes 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 tool with 100% schema coverage and no output schema, the field enumeration effectively substitutes for a return-value description. What is missing (error behavior on unknown ids, read-only nature) is minor given the tool's simplicity.

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 coverage is 100%, with both 'id' and the 'lang' enum already documented in the schema, so the baseline is 3. The description adds no meaning beyond the schema – it never mentions the id lookup or that language selects which core texts are returned.

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

Purpose3/5

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

The description enumerates what the sheet contains (description, origin, themes, uses, care, affirmation, linked chakras), which hints at a per-stone detail lookup, but it never states a verb or that it takes a single stone id. Against siblings like stone_list and stone_image the noun 'sheet' implies a detail view, but the agent must infer that rather than read it.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of when to prefer stone_list or stone_image instead, and no prerequisites stated. The only usage signal is implicit: the schema's 'id from /v1/stones' tells the agent a stone must exist first, but the description contributes nothing.

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