Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

tax_codes_get

Retrieve a tax code by its ID to validate tax settings and apply the correct tax rules to Macola 10 records.

Instructions

Get the Tax Code 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": "tax_codes_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTax code 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?

With no annotations, the description carries the full burden; "Get" does signal a read-only single-record retrieval, the most important behavioral fact. It does not say what happens when the ID does not exist (error vs empty), nor whether all fields of the tax code are returned, so meaningful gaps remain for an unannotated tool.

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 sentence, front-loaded with the verb and resource, with no redundant or filler wording. There is nothing to trim.

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 one-parameter getter this is close to adequate, but with no output schema and no annotations the description should at least indicate the response shape or failure behavior. It covers the happy path only.

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?

Schema description coverage is 100% and the single parameter is fully documented as "Tax code ID"; the description adds nothing beyond confirming that the ID identifies the entry. Baseline 3 applies since the schema does the work.

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?

States a specific verb and resource ("Get the Tax Code") scoped to a single entry identified by ID, which distinguishes it in kind from tax_codes_find's apparent list/search behavior. It stops short of naming that sibling explicitly, so the differentiation is inferred rather than declared.

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 this is the direct-lookup path when the ID is already known, which contrasts implicitly with a find operation. However, there is no explicit when-to-use statement, no guidance for what to do when the ID is unknown, and no named alternative.

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