Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

gl_cost_units_find

Retrieve cost units by General Ledger account or customer number with pagination and filtering for financial analysis and reporting.

Instructions

Get Cost Units. GeneralLedgerAccount or CustomerNumber is required.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
skipNo
orderNo
fieldsNo
distinctNo
divisionNo
pageSizeNo
countOnlyNo
totalCountNo
CustomerNumberNo
GeneralLedgerAccountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden and discloses almost nothing beyond the identifier requirement. It does not state that this is a read-only lookup (only implied by 'Get'), nor does it explain pagination, count-only modes, or what happens if both identifiers are supplied.

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 short, front-loaded sentences with zero filler, and the critical constraint is placed immediately after the purpose. The brevity is intentional rather than padded, though it tips into under-specification.

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

Completeness2/5

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

For an 11-parameter find tool with no annotations, no output schema, and no schema descriptions, this definition is far too thin. An agent still cannot tell what a cost unit is, how results are paged, or how the 'required' identifier statement squares with the schema declaring zero required parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 11 parameters, and the description only touches 2 of them (GeneralLedgerAccount, CustomerNumber). The nine paging/query parameters — page, skip, order, fields, distinct, division, pageSize, countOnly, totalCount — get no meaning at all, so the description does not compensate for the coverage gap.

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

Purpose3/5

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

"Get Cost Units" states a verb and a resource, but it largely restates the tool name and leaves ambiguous what a 'cost unit' actually is. The added sentence that GeneralLedgerAccount or CustomerNumber is required gives some scope, but the description never distinguishes this tool from siblings like gl_cost_centers_find or gl_accounts_find.

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?

It supplies one real usage precondition — that a GeneralLedgerAccount or CustomerNumber must be provided — which is actionable context. However, it offers no when-to-use guidance relative to the many other *_find tools and no exclusions or alternative routing.

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

Deploy Server

Other Tools