Skip to main content
Glama

services_get_change_product_price

Read-onlyIdempotent

Retrieves the prorated price for switching a service to another product in the same group, helping you check change costs before confirming.

Instructions

Get prorated price for switching service to another product in the same group GET /services/{id}/change-product

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

Input Schema

NameRequiredDescriptionDefault
idYes
productIdYesTarget product id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description still earns credit for disclosing two things annotations cannot: the price is prorated, and the target product must belong to the same group. It does not say whether an out-of-group request errors or what the quote includes.

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

Conciseness5/5

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

Two lines, no filler: the capability and its key constraint come first, and the endpoint path is appended as supporting detail. Every clause carries information.

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

Completeness4/5

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

This is a simple two-parameter read tool with no output schema, and the description covers what it computes, the group constraint, and the endpoint. The main residual gap is a total absence of return-shape hints (price amount, currency, proration window), which matters slightly more here because no output schema exists to carry them.

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 50% schema coverage and two required params, the description partially compensates by framing the operation as 'GET /services/{id}/change-product', which implies that `id` is the service id — the parameter the schema leaves undocumented. It adds nothing about `productId` beyond the schema's 'Target product id', and does not reinforce the same-group constraint at the parameter level.

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 gives a specific verb and resource ('Get prorated price') plus the exact operation it prices ('switching service to another product in the same group'), which is enough to distinguish it from the sibling services_get_price (a general price lookup) and services_change_product (the mutation itself). It stops short of naming a sibling explicitly, which keeps it out of 5 territory.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer this is the dry-run quote to fetch before calling services_change_product, but the description never says 'use this before changing the product' or states any exclusion. There is no guidance on what to do if the target product is in a different group.

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