Skip to main content
Glama

services_networks_ipv4_get_price

Read-onlyIdempotent

Retrieves IPv4 network pricing for a specified service ID so you can check costs before provisioning or billing service networks.

Instructions

Services networks ipv4 get price GET /services/{serviceId}/networks/ipv4/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": {
      "serviceId": "<serviceId>"
    },
    "name": "services_networks_ipv4_get_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.6/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered without the description. Beyond that, the description adds nothing — no mention of whether pricing requires an existing service in a particular state, whether volume/period affects the result, or what the returned price represents.

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?

Two short lines with no filler, and the resource is front-loaded. However, the brevity comes at the cost of substance — the second line is a raw route rather than information an agent needs to decide or call correctly.

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 one-parameter read-only price lookup with no output schema and rich annotations, a short definition is defensible; the agent knows it is a safe idempotent read. The missing piece is what the price pertains to and when to prefer it over other price endpoints, which limits it to a 4 rather than lower.

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?

There is a single parameter, serviceId, with 0% schema description coverage, and the description contributes only the path template '{serviceId}'. It does not clarify that serviceId is the numeric service identifier whose IPv4 pricing is being queried, nor any constraints or format, so the parameter remains essentially undocumented.

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 restates the tool name nearly word-for-word ('Services networks ipv4 get price') and appends the HTTP route, which confirms it fetches IPv4 network pricing for a given service. That is enough to grasp the general intent, but it never says what is being priced (per-address cost, monthly fee, additional addresses) or how it differs from siblings like services_get_price or services_networks_ipv4_get_list.

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 when-to-use guidance, no prerequisites, and no mention of an alternative such as services_get_price or services_networks_buy_ipv4. The only context is the raw endpoint path, leaving the agent to infer that this is a pre-purchase pricing lookup.

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