Skip to main content
Glama
Sign In

OrgLines

by com.orglines
OverviewDiscussionsAdmin

Finance: Break-even

fin_break_even
Read-only

The revenue needed to cover everything, with the inputs it was computed from: what counts as fixed, what as variable, against which revenue base, which categories are still unsplit and how many costs carry no category. Optionally answers the inverse — the revenue needed for a target operating profit ('how much must we sell to clear 30000'). Returns null with a reason when there is no revenue base or when variable costs meet or exceed revenue; in both cases no revenue figure would be truthful.

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_break_even"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNoFiscal period id (see fin_periods). Default: the current month.
target_profitNoAsk the inverse question: the revenue needed to earn this much.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only establish read-only safety; the description adds substantive behavior: it returns the inputs behind the calculation, discloses unsplit/no-category cost handling, and states both null conditions with reasons. That is rich context beyond annotations and the absence of an output schema.

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?

Two dense sentences front-load the core revenue figure and then cover inverse mode and null behavior without filler. The first sentence is long but every listed component is relevant to understanding the result.

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

Completeness5/5

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

For a read-only calculation tool with no output schema, the description explains what is returned, what inputs accompany it, and when null is returned and why. Combined with full schema parameter coverage, an agent has enough to invoke it correctly.

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 100%, so the baseline would be 3; the description adds meaning for target_profit by framing it as the inverse revenue question for a target operating profit and gives an example. It does not add detail for period, but the schema already documents it.

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 the computed quantity (revenue needed to cover everything), the inverse mode, and the null-return conditions. This is specific enough for an agent to know it handles break-even revenue rather than cashflow or forecasting.

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?

Explains the target_profit option as the inverse question and gives an example, but does not give broader when-to-use guidance versus sibling finance tools or state when not to use it. Usage is implied by the break-even purpose.

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