Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

gl_cost_centers_find

Find cost centers by GeneralLedgerAccount or CustomerNumber to support Macola general ledger reporting and data lookups, with paging and field filtering.

Instructions

Get Cost Centers. 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_centers_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.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and mostly drops it: nothing about whether an unfiltered call returns everything, how paging behaves, or what the result looks like. It also asserts a requirement that the schema does not enforce (0 required parameters), which an agent could read as an inconsistency rather than as a hint to filter.

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 sentences, front-loaded with the resource and then the constraint, with no filler or repetition. It is efficient, though the brevity is achieved by omitting content rather than by pruning it.

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 query tool with no annotations, no output schema, and zero schema descriptions, the definition leaves most of what an agent needs unanswered. Only the two entity filters are acknowledged; paging, projection, and aggregation behavior are entirely undocumented.

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, so the description must compensate and it does not. It mentions only CustomerNumber and GeneralLedgerAccount, saying merely that one is required, and adds nothing about page, pageSize, skip, order, fields, distinct, division, countOnly, or totalCount.

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 Centers" names the resource clearly, but the verb is generic and never states this is a filtered list/search over 11 paging and filter parameters. It also gives no differentiation from the close sibling "gl_cost_units_find", leaving the agent to guess which entity it returns.

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?

The only guidance is the precondition "GeneralLedgerAccount or CustomerNumber is required", which constrains invocation but says nothing about when to reach for this tool versus gl_cost_units_find or gl_accounts_find. No alternatives, no exclusions, no described use case.

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