Skip to main content
Glama

stone_image

Original illustration of the stone (WebP image). Price: $0.01 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_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesStone id from /v1/stones

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does disclose two valuable traits: the return format (WebP image) and the paid-access model ($0.01 USDC per call via x402). It does not explain how payment is actually settled, what happens on an unpaid or invalid request, or whether the returned illustration is stable per id.

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, zero filler, with the resource and output format front-loaded before the pricing qualifier. Nothing is repeated from the schema or title.

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 one-parameter image fetch with no output schema and no nested objects, the description covers what the tool produces, its format, and its cost. The remaining gaps – payment mechanics and error behavior on unknown ids – are minor for a tool of this 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 description coverage is 100% and the single id parameter is already documented as a 'Stone id from /v1/stones', so the schema does the heavy lifting. The description adds no additional meaning about the id (format, where to obtain it, behavior on unknown ids), which is acceptable at this coverage level but not additive.

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 concrete resource – an original illustration of a stone, delivered as a WebP image – which is specific enough to distinguish it from data-returning siblings like stone_list. However, it never states an explicit verb (fetch/return) and does not differentiate itself from stone_sheet or archetype_card_image, which by name could also return stone artwork.

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 guidance on when to call this rather than stone_sheet, stone_list, or archetype_card_image, and no mention of prerequisites or call ordering. The only usage-adjacent information is the per-call price, which tells the agent it costs money but not when spending it is warranted.

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