aeza-mcp

services_get_prices

Read-onlyIdempotent

Retrieve computed total prices for each payment term of a service by ID from raw product prices to compare billing options.

Instructions

Get computed total price for each payment term from product rawPrices GET /services/{id}/prices

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

Input Schema

Name	Required	Description	Default
`id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 13, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds that the values are computed from product rawPrices and returned per payment term, which is useful behavioral context, but it says nothing about authorization requirements, error cases, or how many terms come back.

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?

It is two terse lines with the purpose front-loaded and no wasted wording. The brevity borders on under-specification rather than padding, but the structure is efficient.

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 read-only lookup with no output schema, the description covers the core purpose and hints at the return shape ('each payment term'). It is still incomplete on what rawPrices means, what the id refers to, and how this differs from the several other price-related siblings.

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 0% for the single required parameter 'id', so the description carries the burden. The REST path 'GET /services/{id}/prices' implicitly indicates that the id is a service identifier, but the description never states this directly or clarifies the expected id type or source.

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 computed total price for each payment term from product rawPrices'. That is meaningfully more precise than the sibling names services_get_price or services_get_change_product_price, though it does not explicitly state how it differs from them.

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 tool rather than services_get_price, services_get_change_product_price, or services_orders_get_price, and no prerequisites or exclusions are stated. The agent must infer usage from the name and the REST path alone.

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

Deploy Server