Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

tax_schedules_find

Find tax schedules in Macola 10 by filtering, paging, and selecting fields to retrieve the records you need.

Instructions

Find Tax Schedules.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
skipNo
orderNo
fieldsNo
distinctNo
divisionNo
pageSizeNo
countOnlyNo
totalCountNo
TaxScheduleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

D1.8/5.0
Behavior1/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 it discloses nothing. It does not mention pagination, default page size, whether countOnly/totalCount change the response shape, or whether this is a read-only operation. For a 10-parameter query tool this is a complete absence of behavioral context.

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

Conciseness2/5

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

The single sentence is short, but this is under-specification rather than conciseness — there is no wasted wording because there is almost no wording. Nothing is front-loaded beyond the bare title, and no structure exists to guide invocation.

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 optional parameters, no annotations, no output schema, and no parameter descriptions, the definition omits everything an agent needs to call the tool correctly. There is no pagination guidance, no countOnly/totalCount explanation, and no hint about return values, which cannot be inferred elsewhere.

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 adds no parameter meaning at all. Terms like skip, fields, distinct, order, and TaxSchedule are left entirely unexplained, so an agent cannot know expected formats or semantics from either source. This is the worst case: high parameter count with zero documentation in both schema and description.

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 verb ("Find") and a resource ("Tax Schedules"), which is enough to know it retrieves tax-schedule records. However, it is essentially a restatement of the tool name and gives no scope detail — no indication of what a tax schedule is, what a result set looks like, or how it differs from the sibling tax_schedules_get. Vague but not misleading.

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 whatsoever: nothing says when to call this versus tax_schedules_get, whether filters are required, or whether it should be used for bulk retrieval. The only signal is the generic "find" naming convention shared across siblings, which is not stated in the definition itself.

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