Skip to main content
Glama

elasticities

Calculate own- and cross-price sensitivity for products on a shelf and return 95% ranges to guide pricing and assortment decisions.

Instructions

Own- and cross-price elasticities for a shelf, with 95% ranges.

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": {
      "fit_id": "<fit_id>",
      "products": "<products>"
    },
    "name": "elasticities"
  }
}

Input Schema

NameRequiredDescriptionDefault
fit_idYes
productsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 discloses one useful trait (results come with 95% ranges), but says nothing about cost, latency, whether a fit must be finished, whether it is a pure read, or what a failure looks like.

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 front-loaded sentence with no filler. It is terse rather than padded, though the terseness comes at the cost of the missing details noted elsewhere.

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

Completeness2/5

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

For a two-required-parameter analytical tool with an unconstrained nested array and no output schema, one clause is not enough. The description should say what fit_id refers to, what a product entry must contain, and roughly what the response looks like.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and both parameters are required, so the description needed to compensate. 'For a shelf' loosely gestures at the products input, but fit_id is never explained and the shape of each product object (schema only says additionalProperties: true) remains entirely undocumented.

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?

Names a specific quantitative output ('own- and cross-price elasticities for a shelf') plus an uncertainty treatment ('95% ranges'), which is enough to tell it apart from forecast, price_sweep or simulate_shares. It stops short of 5 because there is no verb establishing whether it computes elasticities or merely retrieves stored ones.

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?

No when-to-use guidance, no prerequisites, and no named alternatives among the many sibling simulation/forecast tools. An agent must guess that a completed fit is required and cannot tell from the text why it would pick this over price_sweep or forecast.

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