Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

tax_schedules_get

Retrieve a tax schedule by its ID to look up tax details for a specific entry.

Instructions

Get the Tax Schedule 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_schedules_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesTax schedule 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 full burden; "Get" weakly signals a read-only operation but nothing is stated explicitly. It says nothing about what happens when the ID does not exist (error vs empty result) or what fields the returned schedule contains, which matters since there is no output schema.

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 the resource stated before the parameter requirement, and no filler. It is efficient, though the trailing "by specifying its ID" is nearly redundant given the schema's required id field.

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 lookup with full schema coverage, the description is minimally sufficient to invoke the tool. The gap is the missing failure behavior and absence of any hint about the returned record's shape, which the lack of an output schema leaves entirely undocumented.

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 coverage is 100% and the single parameter is documented as "Tax schedule ID", so the description adds no meaning beyond the schema. Its phrasing does confirm the ID refers to a specific entry, but that is a restatement rather than new semantics; 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?

The description names a specific verb and resource (get the Tax Schedule) plus the retrieval key (its ID), so the agent knows exactly what the tool returns conceptually. It does not distinguish itself from the sibling tax_schedules_find, leaving the agent to infer that this is a single-record lookup rather than 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 for use (you already have an ID), which is useful implicit guidance. However, it never states when to prefer this over tax_schedules_find or what to do when no ID is known, so the routing decision is left to inference.

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