Skip to main content
Glama

Mecenai

get_price_rule

Artist-approved price wording for one artwork (e.g. 'price on request', 'from $4,000').

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": {
      "artwork_id": "<artwork_id>"
    },
    "name": "get_price_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
artwork_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It doesn't say whether this is a safe read, whether 'artist-approved' implies any access restriction, or what is returned when no rule exists (empty string, null, error, or a fallback). Those are exactly the unknowns an agent needs resolved before calling.

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 tight sentence with the scope constraint and examples front-loaded; nothing is wasted. The phrase 'price wording' is slightly obscure jargon, but the examples immediately resolve it.

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

Completeness3/5

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

For a one-parameter read tool with no output schema, the description usefully characterizes the return value through examples. It is still incomplete on the empty/no-rule case and on whether the returned wording is display-ready copy versus structured price data.

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 0%, but the single parameter is self-explanatory (artwork_id) and the description's 'for one artwork' confirms the cardinality. It adds no format details (ID vs slug vs numeric string) and nothing about validity or error behavior for unknown IDs.

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 names the resource precisely ('price wording for one artwork') and the parenthetical examples ('price on request', 'from $4,000') make it unmistakable which field is returned, distinguishing it from a generic artwork lookup like find_artworks. It lacks an explicit verb, but the name plus the wording make the operation clear.

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 statement of when to call this versus alternatives, no prerequisites, and no indication of what to do when an artwork has no price wording set. The only implicit guidance is 'one artwork', which hints at per-item lookup rather than bulk retrieval.

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.