Skip to main content
Glama

simulate_removal

Simulate removing one product to see how its shares redistribute to each remaining product and to none, with 95% ranges. Answers the substitution question.

Instructions

Remove one product (0-based index into products): the shares after, and where its buyers go (diversion to each remaining product and to none), with 95% ranges. The substitution question.

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>",
      "remove": "<remove>"
    },
    "name": "simulate_removal"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupNo
fit_idYes
removeYes
productsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/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. It does disclose the output content (shares after removal, diversion split, 95% ranges), which is useful, but it never says whether the removal is a hypothetical simulation or a persistent mutation, whether an existing fit is required, or what permissions/latency apply.

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?

Dense and front-loaded: the action, the output, and the analytic framing each appear once. The parenthetical stacking and the sentence fragment 'The substitution question.' are slightly awkward but no wording is wasted.

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 statistical simulation tool with no annotations, no output schema, and zero schema coverage, the description does describe the return content adequately. It falls short on the fit_id relationship (must a fit exist first?), whether the operation is reversible, and the meaning of 'group' — all material for correct invocation.

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?

With 0% schema description coverage across four parameters, the description partially compensates by defining 'remove' as a 0-based index into 'products' — genuinely valuable indexing information not in the schema. However, 'fit_id' and 'group' receive no explanation at all, leaving half the parameters undocumented anywhere.

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?

States a specific operation (remove one product) and what is returned: post-removal shares plus buyer diversion to each remaining product and to 'none', with 95% ranges. An agent can distinguish this from simulate_shares because the removal scenario is stated explicitly, though the phrasing is compressed into a fragment.

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?

The closing line 'The substitution question' implies when to reach for this tool (substitution/diversion analysis), but there is no explicit when-to-use statement, no exclusions, and no named alternative such as simulate_shares for the non-removal case.

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