Skip to main content
Glama

BRAINIAC Accounting Schedules & Close

Allocate contract price to performance obligations

accounting-schedules_revenue-recognition-schedule
Read-onlyIdempotent

Allocate transaction price by relative standalone selling price and schedule point-in-time, straight-line or milestone recognition by month. Price $0.03 USDC. POST /api/v1/accounting-schedules/revenue-recognition-schedule. An unpaid call returns the x402 payment terms and does not run.

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": {
      "transactionPrice": "<transactionPrice>",
      "obligations": "<obligations>"
    },
    "name": "accounting-schedules_revenue-recognition-schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
obligationsYesobligations, array. Required.
transactionPriceYestransactionPrice, integer, from any to 9007199254740991. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
scheduleNoschedule. Array.
allocationNoallocation. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the cost ($0.03 USDC), the transport (POST with the explicit path), and the unpaid-call behavior (returns x402 payment terms and does not execute). That is meaningful operational context that annotations do not supply, though it does not address idempotency semantics of scheduling or output shape.

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?

Three short sentences that front-load the core function, then pricing and transport details. There is no filler, though the endpoint path and price could be considered operational metadata rather than descriptive value.

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?

Given an output schema exists, return values need not be explained, and the description covers purpose, cost, and payment gating. It is complete enough to invoke safely, with only minor gaps around when the tool should be preferred over sibling schedules.

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 coverage is 100%, so the required transactionPrice and obligations parameters, including the ssp and pattern fields, are already documented in the schema. The description only restates the allocation concept at a high level and adds no format or constraint detail beyond the schema.

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 names a specific verb and resource: allocate transaction price by relative standalone selling price and schedule recognition by month. The recognition patterns (point-in-time, straight-line, milestone) distinguish it from sibling schedule builders such as depreciation or lease schedules.

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 description implies the scenario (allocating a contract price across performance obligations and scheduling revenue), but it never states when to use this versus alternatives or any prerequisites. There is no explicit when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources