Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

forecast_pro_export

Export Macola history data as a CSV file formatted for import into Forecast Pro TRAC, with filters for dates, location, items, customers, categories, and salespeople.

Instructions

Export history data from Macola as a CSV file that can be imported into Forecast Pro TRAC.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "forecast_pro_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
EndDateNo
LocationNo
StartDateNo
StockedItemNo
ItemCategoryNo
ItemNumberEndNo
CalendarNumberNo
SalesPersonEndNo
ItemNumberStartNo
SalesPersonStartNo
CustomerNumberEndNo
ProductCategoryEndNo
CustomerNumberStartNo
ProductCategoryStartNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.6/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 the output format (CSV) but says nothing about whether the file is returned as content or a path, whether the operation is read-only, what permissions are needed, or how the 14 filters affect the export.

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 single sentence is front-loaded, has no filler, and clearly states the output artifact. It is structurally efficient, though the extreme brevity leaves too much unsaid for a 14-parameter tool.

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 14-parameter export tool with no annotations and no output schema, the description is far too thin. It identifies the source, output format, and target system but omits parameter guidance, return behavior, and any operational constraints.

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

Parameters1/5

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

Schema description coverage is 0% and the description does not mention any of the 14 parameters. Names like StartDate and CustomerNumberStart are left completely unexplained, so the description does nothing to compensate for the undocumented schema.

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 states a specific verb and resource: export history data from Macola as a CSV for Forecast Pro TRAC. It is readily distinguishable from forecast_pro_import by the export/import distinction, though it does not explicitly route between them.

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?

It implies the tool is used to prepare data for Forecast Pro TRAC import, but gives no explicit when-to-use guidance, prerequisites, or exclusions relative to the sibling import tool.

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

Deploy Server

Other Tools