Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

receivable_terms_get

Retrieves receivable account terms for a specified terms code or ID, letting you look up payment due details before applying them to customers or transactions.

Instructions

Get the Receivable Accounts Term for a particular entry 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": "receivable_terms_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTerms code/ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/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 burden; the verb 'Get' signals a non-mutating lookup. It says nothing about behavior on an unknown or malformed ID, or about what the term record represents, which matters slightly more than usual without annotation coverage.

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?

A single front-loaded sentence with no filler; the resource and the lookup key both appear immediately. It is appropriately sized for a one-parameter lookup tool.

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?

For a simple single-record getter with full schema coverage, only modest explanation is needed, and the description covers the essential what and how. It omits what a returned terms record contains (no output schema exists) and any error behavior, leaving small but real gaps.

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?

With one parameter and 100% schema description coverage ('Terms code/ID'), the schema already documents the input. The description restates it as 'its ID' without adding format, lookup semantics, or whether the code is case-sensitive, so baseline 3 applies.

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?

Names a specific verb ('Get') and resource ('Receivable Accounts Term') and scopes it to a single entry by ID. It does not explicitly distinguish itself from the sibling receivable_terms_find, so an agent must infer that this is the single-record lookup versus a search.

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?

'by specifying its ID' implies the precondition that the caller already holds an identifier, which is useful context. It gives no explicit when-not guidance or pointer to receivable_terms_find for cases where the ID is unknown.

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