Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

tax_codes_find

Find tax codes in Macola 10 by code, division, or custom fields, with pagination and count options for accurate lookups.

Instructions

Find Tax Codes.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
skipNo
orderNo
fieldsNo
TaxCodeNo
distinctNo
divisionNo
pageSizeNo
countOnlyNo
totalCountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

D1.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden but discloses almost nothing. "Find" weakly implies a non-destructive query, yet nothing is said about pagination behavior, default result limits, ordering, or the meaning of countOnly/totalCount.

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 one-line description is short but under-specified rather than concise; brevity here reflects missing content, not efficient communication. There is no front-loaded scope or structure to build on.

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?

For a 10-parameter query tool with no annotations and no output schema, the description provides essentially nothing an agent needs to call it correctly. All parameter and return-shape information is absent.

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?

Ten parameters exist with 0% schema description coverage, and the description supplies no parameter meaning whatsoever. An agent cannot tell what page, skip, order, fields, distinct, countOnly, or totalCount do from this definition.

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

Purpose2/5

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

"Find Tax Codes" merely restates the tool name (tax_codes_find) without adding scope, filters, or distinguishing it from the sibling tax_codes_get. It does name a concrete verb and resource, so it is not wholly missing, but it is tautological.

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 guidance on when to use this find tool versus tax_codes_get or tax_schedules_find. No exclusions, no prerequisites, no context for selection are provided.

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