Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

forecast_pro_import

Imports a Forecast Pro TRAC XML forecast file into Macola for a specified calendar number and optional location, so forecast data can be loaded into Macola.

Instructions

UNTESTED - do not use without checking first. Import a Forecast Pro TRAC XML forecast file into Macola for a given Calendar Number and optionally a specific Location. (The API spec documents the XML as a required "request" parameter; this tool sends it as the body.)

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": {
      "xmlContent": "<xmlContent>"
    },
    "name": "forecast_pro_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
LocationNo
xmlContentYesThe full Forecast Pro TRAC XML content as a string (will be sent as the request body)
CalendarNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the untested status and the notable quirk that the XML is sent as the request body rather than as the spec's 'request' parameter, but it says nothing about what the import does to existing forecast data (create vs. overwrite), whether it is idempotent, or what errors look 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?

The warning is front-loaded, and the core purpose follows in one tight sentence. The parenthetical about the request-body quirk earns its place as a genuine implementation detail, though it is framed as a note-to-self rather than agent-facing guidance.

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 mutation tool with no annotations and no output schema, the definition covers purpose, parameter roles, and the body-passing quirk. It still leaves the agent without knowledge of side effects, success/failure signaling, or overwrite semantics — a meaningful gap given nothing else supplies that context.

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

Parameters4/5

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

Schema coverage is only 33%; only xmlContent is described in the schema. The description compensates by clarifying that xmlContent must be the full TRAC XML, that Location is an optional narrowing filter, and that Calendar Number is the required scoping key — meaningful semantics not present in the schema for the two undocumented parameters.

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 verb and resource: importing a Forecast Pro TRAC XML forecast file into Macola, scoped by Calendar Number and optional Location. This implicitly distinguishes it from the forecast_pro_export sibling, though it never names that distinction explicitly.

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 'UNTESTED - do not use without checking first' prefix provides a real precondition before calling, which is more than most definitions offer. However, it gives no guidance on when to choose this tool versus other forecast-related paths, nor any prerequisites such as where a valid Calendar Number or TRAC file must come from.

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