Google Play MCP

convert_region_prices

Converts a single tax-exclusive price into Google Play suggested local prices for every region, providing calculator output for regionalConfigs/prices without changing anything.

Instructions

Convert one price into Google's suggested local prices for every region (tax-exclusive input). A calculator only — it changes nothing. Use the output to fill regionalConfigs / prices. price: { currencyCode: 'USD', units: '4', nanos: 990000000 } = $4.99.

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": {
      "packageName": "<packageName>",
      "price": "<price>"
    },
    "name": "convert_region_prices"
  }
}

Input Schema

Name	Required	Description
`price`	Yes	Money: { currencyCode, units (string), nanos (integer) }
`packageName`	Yes	Application id (package name), e.g. com.example.app
`productTaxCategoryCode`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations supplied, the description carries the safety burden and does it well: 'A calculator only — it changes nothing' rules out side effects, and the tax-exclusive constraint is a behavioral fact the agent must know before passing a price. It still leaves out what the returned structure looks like and whether any rounding or region-coverage limits apply.

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?

Three tight sentences: purpose, safety/behavior, usage, then a compact example. No filler, and the most decision-relevant facts (calculator-only, tax-exclusive) come before the illustrative detail.

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?

For a 3-parameter nested-object tool with no output schema, the description tells the agent what the output is for and roughly what it contains ('suggested local prices for every region'). The remaining shortfall is that the response shape is never described concretely and productTaxCategoryCode is left unexplained.

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?

The worked example ({ currencyCode: 'USD', units: '4', nanos: 990000000 } = $4.99) explains the otherwise cryptic units/nanos encoding far beyond the schema's bare type declarations, and 'tax-exclusive input' clarifies the price semantics. The gap is productTaxCategoryCode, which is undocumented in both schema and description at 67% overall coverage.

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

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Convert one price into Google's suggested local prices for every region') and immediately separates itself from the mutation-heavy sibling set with 'A calculator only — it changes nothing.' An agent can tell this is a pure computation tool without opening the schema.

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

Usage Guidelines4/5

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

Gives a clear downstream use case ('Use the output to fill regionalConfigs / prices') and specifies the input basis ('tax-exclusive input'), which tells the agent when this tool is appropriate. It does not name an alternative or an explicit when-not-to-use case, but the read-only framing already rules out the mutation siblings.

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

Deploy Server