Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

receivable_terms_find

Find receivable account terms in Macola by term code, division, fields, ordering, and pagination so you can retrieve the right payment term records.

Instructions

Find Receivable Accounts Terms.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
skipNo
orderNo
fieldsNo
TermCodeNo
distinctNo
divisionNo
pageSizeNo
countOnlyNo
totalCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

D1.9/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, yet it says nothing about read-only semantics, return shape, pagination, or filtering behavior. For a 10-parameter tool this is a critical gap.

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

Conciseness3/5

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

The single short sentence is front-loaded and wastes no words, but its brevity reflects under-specification rather than economy. There is no structure to guide a caller through the many optional parameters.

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

Completeness1/5

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

With 10 undocumented parameters, no annotations, and no output schema, the definition provides essentially nothing an agent needs to invoke the tool correctly. It should at minimum explain the filter parameters and paging behavior.

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% across 10 parameters, and the description explains none of them (page, skip, order, fields, distinct, division, countOnly, totalCount). The agent must guess at paging conventions and the meaning of filter parameters like division or TermCode.

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?

The description names a resource (Receivable Accounts Terms) with a search-style verb (Find), so the general intent is inferable. It does not, however, distinguish this from the sibling receivable_terms_get, leaving the query-vs-single-retrieval boundary ambiguous.

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?

There is no when-to-use guidance, no exclusions, and no pointer to the sibling get tool or any pagination-oriented alternative. The agent is left to infer the use case entirely from the tool name.

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