Skip to main content
Glama
Analog-Labs

Firestarter MCP Server

by Analog-Labs

firestarter_save_address

Save a delivery address to the buyer's address book for reuse on future orders after a purchase or when the buyer requests it, with optional labeling and default setting.

Instructions

Save a delivery address to the buyer's address book for reuse on future orders. Use this after a purchase when the buyer gave a new address, or when they explicitly ask to save an address. Pass an optional label (e.g. 'Home', 'Office', 'Mom's house') — if omitted, a default label is assigned. Set is_default: true to make it the default shipping address for future orders. Returns the saved address id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zipNoPostal / ZIP code
cityYesCity
nameNoRecipient name
labelNoLabel for this address (e.g. 'Home', 'Office', 'Warehouse'). If omitted, a default label is assigned.
phoneNoPhone number for delivery
stateNoState / province / region
countryNoISO country code (e.g. US, PK, KE, NG). ALWAYS pass it when the buyer's country is known or named anywhere in the address — omitting it makes the API infer the country from the address text, falling back to US only as a last resort.
street1YesStreet address line 1
street2NoStreet address line 2 (apt, suite, etc.)
is_defaultNoSet to true to make this the default shipping address.
Behavior4/5

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

Annotations already indicate a non-read-only, non-destructive operation. The description adds useful behavioral context: optional label defaults, is_default behavior, and the return of the saved address id. It does not over-explore side effects, but with annotations present, this is sufficient.

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 three sentences, front-loaded with purpose, then usage, then key behavioral details. It is concise and every sentence serves a purpose, though it slightly restates schema info.

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?

With 10 parameters and no output schema, the description covers the essential purpose, usage, optional label behavior, and return value. It does not explain every parameter, but the schema covers them fully. The return value is stated, which is important without an output schema.

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 the baseline is 3. The description mentions label and is_default behavior, but these are already detailed in the schema. It does not add new parameter semantics beyond what the schema provides.

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 delivery address to the buyer's address book for reuse on future orders. This specific verb+resource combo distinguishes it from siblings like firestarter_save_ship_from, which deals with seller ship-from addresses.

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?

The description provides clear context on when to use this tool: after a purchase when the buyer gives a new address, or when they explicitly ask to save an address. It does not include explicit exclusions or alternative tool names, but the usage timing is well-defined.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Analog-Labs/firestarter-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server