Emailchaser

Set workspace billing profile

set_billing_profile

Idempotent

Creates or replaces the workspace's registrant and postal contact details. Domain registration files these details with the registrar, so every field except addressLineTwo is required; a done-for-you order uses them when it registers domains. Idempotent: sending the same body twice leaves the same state.

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": {
      "firstName": "<firstName>",
      "lastName": "<lastName>",
      "company": "<company>",
      "addressLineOne": "<addressLineOne>",
      "city": "<city>",
      "state": "<state>",
      "postalCode": "<postalCode>",
      "country": "<country>",
      "phoneCc": "<phoneCc>",
      "phone": "<phone>"
    },
    "name": "set_billing_profile"
  }
}

Input Schema

Name	Required	Description
`city`	Yes	City
`phone`	Yes	Phone number without the country code
`state`	Yes	State, province or region
`company`	Yes	Company name
`country`	Yes	ISO 3166-1 alpha-2 country code, e.g. US
`phoneCc`	Yes	Telephone country calling code without the plus, e.g. 1
`lastName`	Yes	Registrant last name
`firstName`	Yes	Registrant first name
`postalCode`	Yes	Postal or ZIP code
`addressLineOne`	Yes	Street address
`addressLineTwo`	No	Suite, floor or unit (optional)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedSep 12, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Goes beyond the annotations by disclosing that these values are filed with the registrar (a public data-disclosure consequence) and by explaining why 10 of 11 fields are mandatory. The idempotency restatement duplicates idempotentHint=true, and no auth or permission requirements are described, keeping it short of a 5.

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

Conciseness4/5

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

Three dense sentences, front-loaded with the operation and its effect. The final idempotency sentence repeats what the annotation already declares, which is the only wasted line; the rationale for required fields earns its place.

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 flat 11-parameter setter with no output schema and full schema coverage, the description supplies the important context: replace semantics, registrar disclosure, and the required-field constraint. Missing only auth prerequisites and any note on what the call returns or verifies.

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?

Schema description coverage is 100%, so field meanings, the country-code format, and which field is optional are all already documented in the schema. The description only restates the required/optional split ('every field except addressLineTwo is required'), adding no format or validation guidance beyond structured data.

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 pair and resource: 'Creates or replaces the workspace's registrant and postal contact details.' This is clearly distinguishable from the sibling get_billing_profile, and the mention of registrar filing and done-for-you orders tells the agent what the data is for.

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 implied rather than stated: the description explains that domain registration and done-for-you orders consume these details, which hints at when to call it, but it never explicitly says when to use this versus alternatives or what prerequisite state (e.g. owning a workspace, permissions) must hold.

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

All Emailchaser 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.

Resources

Need Help?