Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

gl_accounts_find

Find and retrieve Chart of Accounts (GL) records, with filtering, field selection, pagination, and count options for Macola 10 GL account lookups.

Instructions

Find some or all of the Chart of Accounts (GL Accounts).

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

Input Schema

NameRequiredDescriptionDefault
pageNo
skipNo
orderNo
fieldsNo
distinctNo
divisionNo
pageSizeNo
countOnlyNo
totalCountNo
AccountNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.6/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 disclosure burden, yet it says nothing about pagination, ordering, default filters, or result volume. With 10 parameters including page, skip, pageSize, countOnly, totalCount, and distinct, the behavioral surface is large and entirely undisclosed.

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?

One short, front-loaded sentence with no filler or redundancy. Its brevity reflects under-specification rather than waste, but on the narrow measure of conciseness the sentence is efficient.

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?

Given 10 parameters, zero schema documentation, no annotations, and no output schema, the definition is far too thin to call the tool correctly. It clarifies the resource but leaves filtering, paging, and return-shape decisions to guesswork.

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

Parameters1/5

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

Schema description coverage is 0% and the description adds no meaning for any of the 10 parameters. Terms like 'distinct', 'fields', 'order', 'countOnly', and 'AccountNumber' remain unmapped, and the critical ambiguity of whether AccountNumber means an exact match, prefix, or list is unresolved.

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

Purpose4/5

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

The description uses a specific verb ('Find') with a specific resource ('Chart of Accounts (GL Accounts)'), and the parenthetical expands the abbreviation so an agent can link it to the GL domain. It stops short of differentiating from the sibling gl_accounts_get (single-record retrieval), so the boundary is only inferable from the 'some or all' phrasing.

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 phrase 'some or all' hints that the tool supports both unfiltered listing and filtered queries, which is mild contextual guidance. There is no statement of when to prefer this over gl_accounts_get, no mention of required filters or prerequisites, and no exclusions.

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