Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

gl_accounts_get

Retrieve a single general ledger account by its ID to access Chart of Accounts details for Macola 10 business data.

Instructions

Get a single Chart of Account (GL Account) by specifying its ID.

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": {
      "id": "<id>"
    },
    "name": "gl_accounts_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesGL account ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/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; the verb "Get" reasonably conveys a non-mutating read. However, it says nothing about what happens when the ID does not exist, whether auth/permission scoping applies, or what shape the returned account record has.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with zero filler, front-loading the verb and resource immediately. Nothing could be removed without losing information.

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

Completeness3/5

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

There is no output schema, so the description is the only place a caller could learn what the returned GL account contains, and it does not say. For an otherwise trivial single-key lookup the gap is small, but it is a real one.

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?

The schema already documents the single parameter as a "GL account ID" at 100% coverage, and the description's "by specifying its ID" merely restates that. No added detail such as format, example values, or whether it is the internal numeric key vs. an account number.

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?

Specific verb ("Get") plus a clearly named resource ("Chart of Account (GL Account)") and the retrieval key ("by specifying its ID"). The word "single" implicitly separates it from the sibling gl_accounts_find, but the sibling is not named, so differentiation requires the agent to infer it from the find/get naming pattern.

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?

Usage is only implied: one would use this when an ID is already known, and gl_accounts_find when it is not. The description never states that condition or points to the alternative, so the agent must derive the routing rule from sibling names alone.

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