Skip to main content
Glama
Sign In
aeza-mcp

aeza-mcp

by rdydygin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

services_orders_get_price

Read-onlyIdempotent

Calculates the price of a product order using parameters such as payment term, term count, and additional resources, returning total price, items, and discounts before checkout.

Instructions

Get price for product with parameters GET /services/orders/price

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": {
      "productId": "<productId>"
    },
    "name": "services_orders_get_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
productIdYes
termCountNoMultiplier for payment term (e.g. termCount: 24 with term: hour = 24 hours)
paymentTermNomonth
isBackupsEnabledNoDeprecated one-release compatibility: when true, base price fields (totalPrice, items, discount, prolongPrice) return the with-backups values.
additionalResourcesNoAdditional resources beyond product base values (JSON object or query object)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered elsewhere. The description adds nothing beyond restating the HTTP verb and path — no note on pricing currency, whether the quote is time-sensitive, or how termCount/paymentTerm interact with the returned total, all of which would be genuinely new information.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is short and front-loaded, which is good. The second line restating "GET /services/orders/price" is redundant implementation detail that does not help an agent decide or invoke, so the space is not fully earned.

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 five-parameter pricing tool with a nested additionalResources object and no output schema needs the description to explain what kind of price is returned and how the term parameters shape it. Instead the definition is a one-line restatement, leaving the multi-parameter pricing model entirely to the agent's inference.

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

Parameters2/5

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

Schema description coverage is 60%: termCount, paymentTerm, isBackupsEnabled, and additionalResources carry schema-level descriptions, while productId is undocumented. The description contributes no parameter meaning at all — "with parameters" conveys nothing, and it does not explain the semantics of productId or the deprecated-compatibility flag beyond what the schema already says.

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

Purpose3/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 price for product"), so the basic operation is identifiable. However, it does not distinguish this tool from close siblings such as services_get_price, services_get_prices, or services_get_change_product_price, and the trailing phrase "with parameters" is tautological filler.

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 endpoint versus the several other price-related siblings, nor any stated preconditions. The agent must infer the distinction purely from the name and the order-scoped path.

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