Skip to main content
Glama

AIFEC

checkout_set_customer

Read-only

Save the customer's details for this order. Pass every detail in its OWN field, already separated: first_name, last_name, email, phone, line1 (street and number), line2 (floor and door), postcode, city, region, country, company and vat_id. Put only the value in each field, never the label or the sentence around it. Use text only as a last resort, when you cannot tell the details apart. It saves what is valid and returns what it understood, what is wrong and what is still missing. Never invent a value: ask for what was not said.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "checkout_set_customer"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoThe city or town only. Only if the customer gave it.
noteNoA note for the order, only if the customer asked for one
textNoONLY if you cannot separate the details into the fields: what the customer wrote about themselves, exactly as they wrote it. When you pass any separate field, text is ignored.
emailNoThe email address, nothing else. Only if the customer gave it.
line1NoStreet and number only ("Calle Mayor 1", "Carrer de l'Exemple 9"), without the word "address", the floor or the postcode. Only if the customer gave it.
line2NoFloor, door or staircase only ("3º A", "2n 1a", "bajo"), if given. Only if the customer gave it.
phoneNoThe phone number, digits and an optional + prefix. Only if the customer gave it.
regionNoThe province or region, only if given. Only if the customer gave it.
vat_idNoThe tax or VAT ID exactly as given (keep a country prefix such as "ES"), without the label. Only if the customer gave it.
companyNoThe company name ONLY when a company buys and needs the invoice in its name ("Invoice to company X", "Factura a nombre de X"); then vat_id is required too. The name of an office, hotel or association where the parcel is just delivered goes in line2, not here. Send "" to remove a company saved before. Only if the customer gave it.
countryNoISO 3166-1 alpha-2 code ("ES" for Spain). Only if the customer gave it.
postcodeNoThe postcode only. Only if the customer gave it.
last_nameNoThe surname or surnames, nothing else. Only if the customer gave it.
address_idNoOne of the saved_addresses ids of checkout_status (customers with an account)
first_nameNoThe first name of the person, nothing else. Never a greeting, a yes or a label: "Yes", "Ok", "Hello", "Address" or "Name" are not names. Only if the customer gave it.
session_idNoOnly if your client does not keep the MCP session (the Mcp-Session-Id header): the session_id that an earlier answer of this server gave you. It keeps the same cart between calls.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Goes well past the readOnlyHint annotation by disclosing partial-success semantics ('it saves what is valid'), the shape of the response ('what it understood, what is wrong and what is still missing'), and a precedence rule ('When you pass any separate field, text is ignored'). The one tension is that 'Save' implies session state mutation while the annotation claims readOnly, though no order is committed, so it reads as non-destructive cart state rather than a true contradiction.

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?

Front-loaded with the imperative and the field-separation rule, then the fallback rule, then the return contract. Slight redundancy in restating 'put only the value in each field, never the label' on top of per-field guidance, but every sentence carries usable instruction.

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 16-parameter mutator with no output schema, it covers the critical gaps: return contents, partial acceptance, fallback precedence and the no-invention rule. It never mentions address_id or session_id, the two parameters whose interaction with the free-text fields an agent most needs to understand.

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% and the per-field descriptions already carry the disambiguation rules (line1 vs line2, company vs delivery location, country as ISO code). The description reinforces the cross-cutting policy of one detail per field with bare values, but adds no syntax or constraint detail beyond the schema, so baseline 3 applies.

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?

Specific verb plus resource plus scope: 'Save the customer's details for this order', which an agent can immediately tell apart from the shipping, payment and placement siblings. It does not explicitly name a sibling alternative, 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use rule for the ambiguous path ('Use text only as a last resort, when you cannot tell the details apart') and an explicit when-not-to-behave rule ('Never invent a value: ask for what was not said'). It says nothing about routing between this tool and the saved-address flow or when in the checkout sequence to call it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources