Skip to main content
Glama

BRAINIAC Accounting Schedules & Close

FIFO, weighted-average and specific-ID costing

accounting-schedules_inventory-costing
Read-onlyIdempotent

Cost inventory issues under FIFO, perpetual weighted average or specific identification and report closing quantity and value. Price $0.03 USDC. POST /api/v1/accounting-schedules/inventory-costing. 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": {
      "method": "<method>",
      "movements": "<movements>"
    },
    "name": "accounting-schedules_inventory-costing"
  }
}

Input Schema

NameRequiredDescriptionDefault
methodYesmethod, string, one of FIFO, WAVG, SPECIFIC. Required.
movementsYesmovements, array. Required.

Output Schema

NameRequiredDescriptionDefault
issuesNoissues. Array.
methodNomethod. String.
closingNoclosing. Object.
sourcesNosources. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent and non-destructive, but the description adds details they cannot express: a $0.03 USDC price, the POST endpoint, and the unpaid-call flow that returns x402 payment terms without executing. That payment/auth behavior is exactly the kind of trait an agent needs to avoid a failed run.

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, front-loaded with the core purpose before pricing and transport details. The endpoint path and price are justified because they affect invocation, though the URL string is the least valuable element.

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?

With two fully described parameters and an output schema, the description only needs purpose plus invocation constraints, and it covers both including payment gating. The remaining gap is method-selection logic and any lotId requirement for SPECIFIC, which would help but is not strictly essential.

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 both parameters are fully documented in the schema and the baseline is 3. The description restates the method options but does not clarify how movements interact with cost method, e.g. that specific identification plausibly depends on lotId, leaving that inference to 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?

States a specific verb and resource ('Cost inventory issues') plus the three supported methods and the output ('closing quantity and value'). An agent can distinguish this from every sibling, none of which perform inventory valuation.

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

Usage Guidelines2/5

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

No guidance on when to choose FIFO vs WAVG vs SPECIFIC, nor when to use this tool rather than another schedule builder. The only contextual hints are the method names themselves, which the agent must interpret unaided.

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