Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

price_get

Retrieves Macola 10 item price information by customer, quantity, date, currency, and pricing details for quotes, orders, or price validation.

Instructions

Gets Price information for the specified Item, Customer, Quantity, date, etc.

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

Input Schema

NameRequiredDescriptionDefault
PriceDateNo
CurrencyCodeNo
CustomerTypeNo
ExchangeRateNo
PricingDetailNo
CustomerNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description must carry behavioral disclosure and does not. It never states whether the call is read-only or what it computes, such as whether discounts, tax, or FX conversion are applied, or how CurrencyCode and ExchangeRate affect the result.

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?

One short front-loaded sentence with no filler, though the closing 'etc.' is dead weight that adds no meaning. Slight inefficiency, not a structural problem.

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

Completeness2/5

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

A six-parameter pricing lookup with no annotations, no output schema, zero schema coverage, and an undocumented nested PricingDetail array needs far more explanation. An agent cannot tell how the array interacts with the scalar Customer/Quantity fields or what it gets back.

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?

With 0% schema coverage, the description carries the whole burden, and it names most of the relevant inputs: item, customer, quantity, and date. It says nothing about CurrencyCode, ExchangeRate, CustomerType, or the PricingDetail array of line objects, leaving the nested structure unexplained.

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: 'Gets Price information' for a specified item/customer/quantity/date. That is enough to separate it from the sibling *_get tools, which fetch other ERP entities, but the trailing 'etc.' weakens the scope statement.

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?

No guidance on when to use this versus alternatives such as customer_items_get or customer_orders_get, and no prerequisites are stated. The only usage signal is the implicit invocation context of 'I need a price', which the agent must infer.

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