Skip to main content
Glama
Sign In

OrgLines

by com.orglines
OverviewDiscussionsAdmin

Finance: Upcoming obligations

fin_upcoming_obligations
Read-only

What has to be paid next, largest first: recurring commitments, accrued payroll and approved purchase requests, each with its due date, amount and currency. Answers 'show me the big payments next month'. Only what is still expected is listed: an obligation an invoice already carries appears for the REMAINDER after it, and one paid in full does not appear at all — the ledger has that money. isLowerBound on a row means part of that charge cannot be priced yet, so the real figure can only be higher; quote it as a minimum, never as the amount.

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

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 20.
sinceNoStart date YYYY-MM-DD. Default: today.
untilNoEnd date YYYY-MM-DD. Default: +30 days.
min_amountNoOnly obligations at or above this.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the read-only annotations, the description discloses ordering, inclusion rules, netting behavior for invoiced obligations, complete omission of paid items, and the meaning of isLowerBound as a minimum. These are material behavioral traits an agent would not get from annotations or schema alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is front-loaded with purpose and ordering, then moves through use case, inclusion rules, and the isLowerBound caveat. Every sentence carries specific operational meaning without repetition or filler.

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?

There is no output schema, but the description explains the relevant returned fields and caveats, including due date, amount, currency, and isLowerBound. Combined with complete input schema coverage and read-only annotations, it gives an agent enough to call and interpret the tool correctly.

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%, so limit, since, until, and min_amount are already documented in the input schema. The description does not add parameter-specific syntax or edge-case meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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?

The description states a specific resource and output: upcoming obligations to be paid, largest first, covering recurring commitments, accrued payroll, and approved purchase requests with due date, amount, and currency. It distinguishes the tool from narrower siblings like fin_recurring_list and fin_purchase_requests by aggregating and netting expected payments.

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?

It gives a clear use context with the example query 'show me the big payments next month,' which tells an agent when this tool fits. It does not explicitly name alternatives or when-not-to-use cases, so it stops short of full routing guidance.

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