Skip to main content
Glama

simulate_shares

Calculates share of preference for a product shelf from a conjoint fit, returning 95% ranges for up to 60 products and optional covariate groups.

Instructions

Share of preference for a shelf, with 95% ranges. products: up to 60, each {attribute: level} with levels exactly as in the design (price any number in the tested range). group: a covariate group, if the fit has them.

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": "simulate_shares"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupNo
fit_idYes
productsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden. It usefully discloses that results come with 95% ranges and that levels must match the design exactly (a real failure mode), but says nothing about whether the call persists state, how expensive or slow a simulation is, or what happens when a product violates the design constraints.

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 compact sentences with the purpose front-loaded and per-parameter notes following; nothing is padded. The telegraphic phrasing ('group: a covariate group, if the fit has them') is efficient but slightly terse.

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 three-parameter simulation tool with no output schema and no annotations, the description gives enough to construct a valid call and anticipate a ranged share output. It leaves open what fit_id refers to, whether results are stored or ephemeral, and how constraint violations are surfaced, which are material gaps given the absence of annotations.

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%, so the description must compensate. It does well on products (up to 60, map of attribute to level, levels must match the design, price may be any number in the tested range) and partially on group (a covariate group, optional if the fit has them), but adds nothing about fit_id beyond its name.

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 a specific computed quantity (share of preference for a shelf) and its output form (95% ranges), which is far more informative than the name alone. It does not explicitly contrast with simulate_removal or price_sweep, so an agent must infer which simulation tool applies.

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 only implied by the stated inputs and limits; there is no explicit 'use this when...' or 'do not use for...' guidance, and no named alternative for related questions like removal or price sweeps. The constraints given (up to 60 products, levels matching the design, price within the tested range) do constrain when the call will succeed, which lifts it above pure silence.

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