Skip to main content
Glama
Sign In

OrgLines

by com.orglines
OverviewDiscussionsAdmin

Finance: Forecast variance

fin_forecast_variance
Read-only

Budget against forecast for a period, and which side moved: the gap on income, on spend and on profit. Answers 'why is the November profit below what we planned'. Refuses the comparison outright when there is no approved budget, when the budget is in a different currency, or when the forecast could not be reduced to one currency — a missing rate must never be reported as agreement with the plan.

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

Input Schema

NameRequiredDescriptionDefault
periodNoFiscal period id (see fin_periods). Default: the current month.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only say readOnly/no-side-effects; the description goes well beyond by enumerating hard refusal conditions (no approved budget, budget in a different currency, forecast not reducible to one currency). It also states the design principle that a missing FX rate must never be reported as agreement with plan, which warns the agent off misreading a failure as a zero-variance result.

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?

Front-loads the purpose and the returned breakdown, then closes with the refusal rules where they belong. The final clause is long and appositive-heavy, but every element carries behavioral information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read-only tool with annotations and no output schema, it covers purpose, output components, and failure modes. It leaves the shape of the returned figures (magnitudes vs signed deltas, formatting) unstated, which is the only meaningful gap.

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 100% and the single param documents the fiscal period id and its default. The description only refers to 'a period' generically, adding no format or lookup detail beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific resource and comparison (budget vs forecast for a period) and the exact decomposition returned (gap on income, spend, profit). The worked example question ('why is the November profit below what we planned') pins the semantics down without needing the schema opened.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear triggering context: an agent should reach for this when a user asks why actuals diverged from plan for a period. It does not explicitly name alternatives (e.g. fin_overview, fin_scenario_compare) or state exclusions, so routing against siblings is only implied.

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

All OrgLines toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources