Skip to main content
Glama
merit-aktiva-mcp

merit-aktiva-mcp

by lauri911

Merit Sales Prices

merit_sales_prices
Read-only

Retrieves sales price lists, discount rules, or the valid price and discount for a specific customer, item, and date from Merit.

Instructions

Sales prices and discounts kept in Merit: the price lists, the discount rules, or the price one customer gets for an item on a date.

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": {
      "kind": "<kind>"
    },
    "name": "merit_sales_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesprice_list: all sales prices set per item; discounts: all discount rules; customer_price: the price and discount valid for one customer, item and date
unitNocustomer_price: unit of measure
limitNoMax rows to return (totals still cover all)
searchNoprice_list/discounts: only rows whose item, group or name contains this
on_dateNocustomer_price: price valid on this date; default today
currencyNocustomer_price: currency; default the company's
item_codeNocustomer_price: the item code (required)
customer_idNocustomer_price: CustomerId (or give customer_reg_no or customer_name)
customer_nameNocustomer_price: the customer's exact name
customer_reg_noNocustomer_price: the customer's registry code

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful domain behavior — that prices are date-effective for a specific customer and item — but says nothing about paging behavior, the fact that totals cover all rows regardless of limit, or the practical requirement to identify a customer before a customer_price lookup.

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 no filler; the three-way enumeration is efficient and scannable. "Kept in Merit" is the only soft phrase and could be dropped for a crisper verb.

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?

With 10 parameters, a required kind discriminator, and mode-specific conditionals, the definition is thin — a reader must go to the schema to learn that item_code is required for customer_price or that limit defaults to 300. An output schema exists, so return-value explanation is not needed, which keeps it at a viable 3 rather than lower.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema carries the parameter burden and the baseline is 3. The description goes slightly beyond by framing each kind's semantics (per-item lists, rule sets, and a point-in-time customer price), reinforcing which parameters belong to which mode.

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 resource and enumerates its three shapes — "the price lists, the discount rules, or the price one customer gets for an item on a date" — which maps directly onto the kind enum and separates it from invoice/offer siblings. It lacks an explicit verb ("retrieve"/"look up"), so it reads as a data label rather than an action, but an agent can still tell what it would get back.

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 stated when-to-use or when-not-to-use guidance, and no alternative is named. The only hint is that the sentence's three clauses correspond to the three kind values, which implies mode selection but gives no criteria for choosing between them or versus other Merit tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.