bitroad

Addresses create

addresses_create

Save a new shipping address. Set is_default_shipping=true to make it the default.

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": {
      "recipient_name": "<recipient_name>",
      "line1": "<line1>",
      "town": "<town>",
      "postcode": "<postcode>",
      "country": "<country>",
      "is_default_shipping": "<is_default_shipping>"
    },
    "name": "addresses_create"
  }
}

Input Schema

Name	Required	Description	Default
`town`	Yes	Town or city.
`line1`	Yes	First address line (street address).
`line2`	No	Second address line, if any.
`phone`	No	Contact phone number for delivery, if any.
`region`	No	Two-letter US state code (e.g. CA); required for country=US, unused for GB.
`country`	Yes	Destination country code: GB (default) or US.	GB
`postcode`	Yes	UK postcode for GB; US ZIP as 12345 or 12345-6789.
`recipient_name`	Yes	Full name of the delivery recipient.
`is_default_shipping`	Yes	When true, make this the buyer's default shipping address. Defaults to false.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 7, 2026

TDQS

A4/5.0

Behavior4/5

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

The description discloses the core write behavior and the effect of is_default_shipping, going slightly beyond the annotations. It does not discuss idempotency or failure modes, but the create action is clearly conveyed.

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?

The description is two short sentences, front-loads the primary action, and avoids unnecessary detail. It is concise and well structured.

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?

The description, combined with the detailed schema, gives enough context to invoke the tool correctly. It does not describe the return value, but no output schema is provided and the action is simple.

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?

The input schema already provides full descriptions for all parameters, so the tool description adds little beyond restating the default flag behavior. Schema coverage is 100%, so baseline is appropriate.

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?

The description clearly states the tool saves a new shipping address, which is a specific verb-resource action. The sibling tool addresses_list is distinct, and the name and description leave no ambiguity about the tool's purpose.

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?

The description implies use when creating a new shipping address, but it does not explicitly contrast with addresses_list or mention when an alternative should be used. The guidance is adequate but not explicit.

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

All bitroad tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.