Skip to main content
Glama

services_networks_buy_ipv4

Destructive

Buys an IPv4 address for a specified service by submitting the service ID along with method and domain details.

Instructions

Buy IPv4 address for service POST /services/{serviceId}/networks/ipv4

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>",
      "body": "<body>"
    },
    "name": "services_networks_buy_ipv4"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
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?

Annotations already flag this as destructive, non-idempotent and open-world, so the description's job is to add context — yet it says nothing about billing implications of a purchase, whether the address is assigned immediately, or that a repeat call buys another address rather than being idempotent. It only restates the endpoint.

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 purpose is front-loaded, but the brevity reflects under-specification rather than efficiency given the purchase semantics and nested body.

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 destructive, chargeable mutation with a nested required body and no output schema, the description leaves too much open: what "method" and "domain" mean, what is returned, and what failures (insufficient funds, quota) look like. Only the endpoint mapping is complete.

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% and the nested body object requires "method" and "domain" with no explanation anywhere. The phrase "for service" minimally hints at serviceId, but the most consequential parameters are undocumented in both schema and description.

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?

States a concrete verb and resource ("Buy IPv4 address for service") plus the underlying endpoint, which clearly separates it from sibling reads like services_networks_ipv4_get_list and price lookups like services_networks_ipv4_get_price. It does not explicitly name the sibling it differs from, so it stops short of a 5.

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 versus services_networks_change_ipv4, services_networks_ipv4_get_price, or the IPv6 alternatives, and no mention of prerequisites such as checking price or available quota first. The agent must infer the workflow 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

Other Tools