Skip to main content
Glama

forecast

Simulates units, revenue, and profit with 95% ranges; compares results to a base shelf and estimates the chance of clearing a hurdle using product, occasion, price, and unit-cost inputs.

Instructions

Units, revenue and profit with 95% ranges, the change against a base shelf and the chance of clearing a hurdle. request: products, occasions, prices, unit_costs, own (indexes), optional base and hurdle (see api_reference).

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>",
      "request": "<request>"
    },
    "name": "forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
fit_idYes
requestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description must carry the full behavioral burden. It discloses output metrics and confidence ranges, but it never says whether the call is read-only or creates state, what permissions are required, or how errors and long-running fits behave.

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?

The text is compact and front-loads output metrics before the request ingredients, with no filler. The first sentence is a verbless fragment and the request list is terse to the point of opacity, but it remains appropriately sized.

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 complex forecasting call with a nested request object and no output schema, the definition gives only a partial picture: outputs are sketched, request fields are listed, and api_reference is offered for base/hurdle. It omits fit_id's role and does not fully specify the request structure, leaving important gaps for an agent to resolve.

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?

The schema has 0% description coverage and exposes only fit_id plus an open-ended request object. The description adds concrete request field names (products, occasions, prices, unit_costs, own, optional base/hurdle) and points to api_reference, but it never explains fit_id or the types and meaning of 'own' and the optional fields.

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 identifies the forecast outputs specifically: units, revenue, profit with 95% ranges, change against a base shelf, and chance of clearing a hurdle. It does not explicitly contrast with siblings such as price_sweep or elasticities, so it stops short of a 5.

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 use this tool versus price_sweep, elasticities, or other siblings, and no prerequisites or exclusions. The only guidance is 'see api_reference' for optional base and hurdle inputs, which is a parameter pointer rather than usage guidance.

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