aeza-mcp

services_resources_get_additional_resources_price

Read-onlyIdempotent

Calculates the price of additional server resources relative to the base tariff, using resource slugs and new amounts so you can estimate costs before changing a plan.

Instructions

Get additional resources price POST /services/{id}/additional-resources/get-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": {
      "id": "<id>",
      "body": "<body>"
    },
    "name": "services_resources_get_additional_resources_price"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`body`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 13, 2026

TDQS

C2.6/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 covered. The description adds nothing beyond restating the endpoint: it does not say this is a dry-run quote, whether the result depends on current base tariff, or whether any state changes. With annotations carrying the load, this barely clears the minimum.

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?

It is short and front-loaded with the human-readable purpose, but the second line simply repeats the HTTP route, which adds little for an agent that already has the tool name. No waste, but no real substance either.

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?

For a tool with a nested object body, zero schema coverage on the key id parameter, and no output schema, the description should explain what the returned price represents (total, per-resource breakdown, currency) and what id refers to. Neither is addressed, leaving the agent to guess at call correctness and result interpretation.

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 top level; the nested additionalResources property does carry a description, but the required 'id' parameter is documented nowhere. The endpoint template only weakly implies that id is a service identifier, and the description itself supplies no parameter meaning.

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 states a specific verb and resource: retrieving the price of additional resources for a service, with the endpoint path reinforcing the scope. It does not differentiate itself from siblings such as services_resources_add_additional_resources or services_get_prices, so an agent must infer whether this is a quote-only or ordering operation.

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 statement of when to use this tool versus the sibling price tools, no precondition (e.g. service must exist, resources must be addable), and no note that this only quotes a price rather than applying it. Usage must be inferred entirely from the name.

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

Deploy Server