Skip to main content
Glama

Hands for Agents

Request a quote

request_quote

Creates a request for a fixed-price quote from a human. The request is not binding and nothing is charged. Required: description, email and name (the person or company on the invoice, normally the recipient or company in delivery_address). delivery_address is needed when a physical item is shipped, handed over or collected: one plain string with recipient, street, postcode and city, country; a phone number is optional. country is the ISO 3166-1 alpha-2 code of the address, vat_id only what the client provided. The fields are sent flat, as in the examples. Returns quote_id (of the form q_..., issued only in this response), access_token (shown once; the only key to the quote and its task), nda_url and upload_url (the address input files are POSTed to). A human answers within 24 hours, every day, with a quote or a refusal. No authentication. Shortest possible request: {"description":"Make 20 rubber gaskets, 60 mm outer diameter, black EPDM.","email":"ops@example.com","name":"Example Inc."}. With a delivery address and an input file: {"description":"Make 20 rubber gaskets, 60 mm outer diameter, black EPDM.","email":"ops@example.com","name":"Example Inc.","delivery_address":"Example GmbH, Musterstr. 1, 10115 Berlin, DE, +49 30 000000","input_files":["https://example.com/gasket-drawing.pdf"]}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesRequired. The person or company on the invoice, normally the recipient or company in delivery_address.
emailYesContact e-mail of the operator; the quote is sent here.
vat_idNoVAT or tax id for the invoice, as given by the client. Optional.
countryNoOperator's country, ISO 3166-1 alpha-2, upper case, normally that of the delivery address. Optional.
currencyNoEUR or USD. Default EUR.
deadlineNoLatest acceptable delivery date, ISO 8601. Optional.
servicesNoService ids. Optional.
agent_nameNoName of the agent or platform. Optional.
descriptionYesWhat is to be done, plainly: quantity, material, colour, size, tolerances, what counts as done.
input_filesNoHTTPS URLs of input files (photos, sketch, STEP/STL model, PDF drawing). At most 20.
deliverablesNoWhat the client expects to receive. Optional; otherwise part of description.
delivery_addressNoRequired for a physical shipment. One plain string: recipient, street, postcode and city, country, as given by the client; a phone number last is optional.
allow_anonymised_exampleNoConsent to publish this task as an anonymised example; true only when the client explicitly agreed. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • changedInput schema / properties / allow_anonymised_example / description
      Previous value: -"Consent to publish this task as an anonymised example. Only true if the client explicitly agreed. Default false."New value: +"Consent to publish this task as an anonymised example; true only when the client explicitly agreed. Default false."
    • changedInput schema / properties / country / description
      Previous value: -"Operator's country, ISO 3166-1 alpha-2, upper case. Optional."New value: +"Operator's country, ISO 3166-1 alpha-2, upper case, normally that of the delivery address. Optional."
    • changedInput schema / properties / deliverables / description
      Previous value: -"What you expect to receive. Optional; otherwise put it in description."New value: +"What the client expects to receive. Optional; otherwise part of description."
    • changedInput schema / properties / delivery_address / description
      Previous value: -"Required for a physical shipment. One plain string: recipient, street, postcode and city, country (only what the user gave; never invent one); a phone number last is optional."New value: +"Required for a physical shipment. One plain string: recipient, street, postcode and city, country, as given by the client; a phone number last is optional."
    • changedInput schema / properties / description / description
      Previous value: -"What is to be done, plainly: everything the user told you (quantity, material, colour, size, tolerances, what counts as done)."New value: +"What is to be done, plainly: quantity, material, colour, size, tolerances, what counts as done."
    • changedInput schema / properties / email / description
      Previous value: -"Contact e-mail of the operator; the quote goes here."New value: +"Contact e-mail of the operator; the quote is sent here."
    • changedInput schema / properties / name / description
      Previous value: -"Required. The name of the person or company for the invoice."New value: +"Required. The person or company on the invoice, normally the recipient or company in delivery_address."
    • changedInput schema / properties / services / description
      Previous value: -"Service ids, if you know them."New value: +"Service ids. Optional."
    • changedInput schema / properties / vat_id / description
      Previous value: -"VAT or tax id for the invoice, only if the user gave it; never guess. Optional."New value: +"VAT or tax id for the invoice, as given by the client. Optional."
  2. Changed2 schema fields changed
    • changedInput schema / properties / delivery_address / description
      Previous value: -"Required for a physical shipment. One plain string: recipient, street, postcode and city, country; a phone number last is optional."New value: +"Required for a physical shipment. One plain string: recipient, street, postcode and city, country (only what the user gave; never invent one); a phone number last is optional."
    • changedInput schema / properties / vat_id / description
      Previous value: -"VAT or tax id for the invoice. Optional."New value: +"VAT or tax id for the invoice, only if the user gave it; never guess. Optional."
  3. Changed17 schema fields changed
    • removedInput schema / properties / agent
      Removed value: -{
      -  "properties": {
      -    "name": {
      -      "description": "Name of the agent or platform sending the request. Optional, for our records.",
      -      "maxLength": 200,
      -      "type": "string"
      -    }
      -  },
      -  "type": "object"
      -}
    • changedInput schema / properties / agent_name / description
      Previous value: -"Flat form of agent.name."New value: +"Name of the agent or platform. Optional."
    • changedInput schema / properties / allow_anonymised_example / description
      Previous value: -"Consent to publish this task as an anonymised example (no names, addresses or personal data), under the confidentiality section of the terms of service. Only set true if the client explicitly agreed to this; otherwise omit the field or leave it false. Default false; can be withdrawn."New value: +"Consent to publish this task as an anonymised example. Only true if the client explicitly agreed. Default false."
    • removedInput schema / properties / client
      Removed value: -{
      -  "properties": {
      -    "country": {
      -      "description": "Country of the operator, ISO 3166-1 alpha-2 (upper case). Optional, but include it whenever you can derive it (for example from the operator's address) rather than leaving it out or asking the user.",
      -      "pattern": "^[A-Z]{2}$",
      -      "type": "string"
      -    },
      -    "email": {
      -      "description": "E-mail of the operator. The quote, the payment link and the invoice go here.",
      -      "format": "email",
      -      "maxLength": 254,
      -      "pattern": "^[^\\s@]+@[^\\s@]+\\.[^\\s@]+$",
      -      "type": "string"
      -    },
      -    "name": {
      -      "description": "Full name of the person, or registered name of the company, that operates the agent. Optional, but include it whenever you know it (for example from a company name or address already in the conversation) rather than leaving it out or asking the user.",
      -      "maxLength": 200,
      -      "minLength": 1,
      -      "pattern": "^[^\\r\\n]+$",
      -      "type": "string"
      -    },
      -    "vat_id": {
      -      "description": "VAT or tax id of the operator, printed on the invoice. Optional.",
      -      "maxLength": 32,
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "email"
      -  ],
      -  "type": "object"
      -}
    • changedInput schema / properties / country / description
      Previous value: -"Flat form of client.country."New value: +"Operator's country, ISO 3166-1 alpha-2, upper case. Optional."
    • changedInput schema / properties / currency / description
      Previous value: -"Flat form of task.currency."New value: +"EUR or USD. Default EUR."
    • changedInput schema / properties / deadline / description
      Previous value: -"Flat form of task.deadline."New value: +"Latest acceptable delivery date, ISO 8601. Optional."
    • changedInput schema / properties / deliverables / description
      Previous value: -"Flat form of task.deliverables."New value: +"What you expect to receive. Optional; otherwise put it in description."
    • changedInput schema / properties / delivery_address / description
      Previous value: -"Flat form of task.delivery_address."New value: +"Required for a physical shipment. One plain string: recipient, street, postcode and city, country; a phone number last is optional."
    • changedInput schema / properties / description / description
      Previous value: -"Flat form of task.description."New value: +"What is to be done, plainly: everything the user told you (quantity, material, colour, size, tolerances, what counts as done)."
    • changedInput schema / properties / email / description
      Previous value: -"Flat form of client.email."New value: +"Contact e-mail of the operator; the quote goes here."
    • changedInput schema / properties / input_files / description
      Previous value: -"Flat form of task.input_files."New value: +"HTTPS URLs of input files (photos, sketch, STEP/STL model, PDF drawing). At most 20."
    • changedInput schema / properties / name / description
      Previous value: -"Flat form of client.name."New value: +"Required. The name of the person or company for the invoice."
    • changedInput schema / properties / services / description
      Previous value: -"Flat form of task.services."New value: +"Service ids, if you know them."
    • removedInput schema / properties / task
      Removed value: -{
      -  "properties": {
      -    "currency": {
      -      "description": "Currency of the quote. Default EUR.",
      -      "enum": [
      -        "EUR",
      -        "USD"
      -      ],
      -      "type": "string"
      -    },
      -    "deadline": {
      -      "description": "Latest acceptable delivery or dispatch date (ISO 8601). Optional; omit if the user gave none.",
      -      "format": "date",
      -      "maxLength": 32,
      -      "type": "string"
      -    },
      -    "deliverables": {
      -      "description": "What you expect to receive (item, files, report, photos, video). Optional - if you are not sure, leave it out and put it in task.description instead.",
      -      "maxLength": 5000,
      -      "type": "string"
      -    },
      -    "delivery_address": {
      -      "description": "Required whenever deliverables describes a physical item to be shipped, packed and collected, or handed over in person - omit only for purely digital deliverables (files, a report). One plain string with name, street, city, postcode and country, in that order; add a phone number at the end only if you already have one. Phone is optional - if you already have a name and an address, never stop to ask the user for a phone number. Not an object and not a list of lines.",
      -      "maxLength": 1000,
      -      "type": "string"
      -    },
      -    "description": {
      -      "description": "What is to be done, in plain language. Include quantities, materials, tolerances and what counts as done.",
      -      "maxLength": 20000,
      -      "type": "string"
      -    },
      -    "input_files": {
      -      "description": "HTTPS URLs of input files, for example photos, a sketch, a CAD model (STEP, STL), a PDF drawing, or other instructions, or attach the files to the e-mail. At most 20, each at most 2000 characters.",
      -      "items": {
      -        "maxLength": 2000,
      -        "pattern": "^https://",
      -        "type": "string"
      -      },
      -      "maxItems": 20,
      -      "type": "array"
      -    },
      -    "services": {
      -      "description": "Service ids from the service list, if you know them.",
      -      "items": {
      -        "enum": [
      -          "design",
      -          "make",
      -          "assemble",
      -          "measure",
      -          "test",
      -          "verify",
      -          "ship"
      -        ],
      -        "type": "string"
      -      },
      -      "type": "array"
      -    }
      -  },
      -  "required": [
      -    "description"
      -  ],
      -  "type": "object"
      -}
    • changedInput schema / properties / vat_id / description
      Previous value: -"Flat form of client.vat_id."New value: +"VAT or tax id for the invoice. Optional."
    • addedInput schema / required
      Added value: +[
      +  "description",
      +  "email",
      +  "name"
      +]
  4. Changed12 schema fields changed
    • changedInput schema / properties / agent_name / description
      Previous value: -"Name of the agent or platform sending the request. Optional, for our records."New value: +"Flat form of agent.name."
    • changedInput schema / properties / country / description
      Previous value: -"Country of the operator, ISO 3166-1 alpha-2 (upper case). Optional, but include it whenever you can derive it (for example from the operator's address) rather than leaving it out or asking the user."New value: +"Flat form of client.country."
    • changedInput schema / properties / currency / description
      Previous value: -"Currency of the quote. Default EUR."New value: +"Flat form of task.currency."
    • changedInput schema / properties / deadline / description
      Previous value: -"Latest acceptable delivery or dispatch date (ISO 8601). Optional; omit if the user gave none."New value: +"Flat form of task.deadline."
    • changedInput schema / properties / deliverables / description
      Previous value: -"What you expect to receive (item, files, report, photos, video). Optional - if you are not sure, leave it out and put it in task.description instead."New value: +"Flat form of task.deliverables."
    • changedInput schema / properties / delivery_address / description
      Previous value: -"Required whenever deliverables describes a physical item to be shipped, packed and collected, or handed over in person - omit only for purely digital deliverables (files, a report). One plain string with name, street, city, postcode and country, in that order; add a phone number at the end only if you already have one. Phone is optional - if you already have a name and an address, never stop to ask the user for a phone number. Not an object and not a list of lines."New value: +"Flat form of task.delivery_address."
    • changedInput schema / properties / description / description
      Previous value: -"What is to be done, in plain language. Include quantities, materials, tolerances and what counts as done."New value: +"Flat form of task.description."
    • changedInput schema / properties / email / description
      Previous value: -"E-mail of the operator. The quote, the payment link and the invoice go here."New value: +"Flat form of client.email."
    • changedInput schema / properties / input_files / description
      Previous value: -"HTTPS URLs of input files, for example photos, a sketch, a CAD model (STEP, STL), a PDF drawing, or other instructions, or attach the files to the e-mail. At most 20, each at most 2000 characters."New value: +"Flat form of task.input_files."
    • changedInput schema / properties / name / description
      Previous value: -"Full name of the person, or registered name of the company, that operates the agent. Optional, but include it whenever you know it (for example from a company name or address already in the conversation) rather than leaving it out or asking the user."New value: +"Flat form of client.name."
    • changedInput schema / properties / services / description
      Previous value: -"Service ids from the service list, if you know them."New value: +"Flat form of task.services."
    • changedInput schema / properties / vat_id / description
      Previous value: -"VAT or tax id of the operator, printed on the invoice. Optional."New value: +"Flat form of client.vat_id."
  5. Changed18 schema fields changed
    • addedInput schema / properties / agent_name
      Added value: +{
      +  "description": "Name of the agent or platform sending the request. Optional, for our records.",
      +  "maxLength": 200,
      +  "type": "string"
      +}
    • changedInput schema / properties / client / properties / country / description
      Previous value: -"Country of the operator, ISO 3166-1 alpha-2 (upper case)."New value: +"Country of the operator, ISO 3166-1 alpha-2 (upper case). Optional, but include it whenever you can derive it (for example from the operator's address) rather than leaving it out or asking the user."
    • changedInput schema / properties / client / properties / name / description
      Previous value: -"Full name of the person, or registered name of the company, that operates the agent."New value: +"Full name of the person, or registered name of the company, that operates the agent. Optional, but include it whenever you know it (for example from a company name or address already in the conversation) rather than leaving it out or asking the user."
    • changedInput schema / properties / client / required
      Previous value: -[
      -  "email",
      -  "name",
      -  "country"
      -]New value: +[
      +  "email"
      +]
    • addedInput schema / properties / country
      Added value: +{
      +  "description": "Country of the operator, ISO 3166-1 alpha-2 (upper case). Optional, but include it whenever you can derive it (for example from the operator's address) rather than leaving it out or asking the user.",
      +  "pattern": "^[A-Z]{2}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / currency
      Added value: +{
      +  "description": "Currency of the quote. Default EUR.",
      +  "enum": [
      +    "EUR",
      +    "USD"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / deadline
      Added value: +{
      +  "description": "Latest acceptable delivery or dispatch date (ISO 8601). Optional; omit if the user gave none.",
      +  "format": "date",
      +  "maxLength": 32,
      +  "type": "string"
      +}
    • addedInput schema / properties / deliverables
      Added value: +{
      +  "description": "What you expect to receive (item, files, report, photos, video). Optional - if you are not sure, leave it out and put it in task.description instead.",
      +  "maxLength": 5000,
      +  "type": "string"
      +}
    • addedInput schema / properties / delivery_address
      Added value: +{
      +  "description": "Required whenever deliverables describes a physical item to be shipped, packed and collected, or handed over in person - omit only for purely digital deliverables (files, a report). One plain string with name, street, city, postcode and country, in that order; add a phone number at the end only if you already have one. Phone is optional - if you already have a name and an address, never stop to ask the user for a phone number. Not an object and not a list of lines.",
      +  "maxLength": 1000,
      +  "type": "string"
      +}
    • addedInput schema / properties / description
      Added value: +{
      +  "description": "What is to be done, in plain language. Include quantities, materials, tolerances and what counts as done.",
      +  "maxLength": 20000,
      +  "type": "string"
      +}
    • addedInput schema / properties / email
      Added value: +{
      +  "description": "E-mail of the operator. The quote, the payment link and the invoice go here.",
      +  "format": "email",
      +  "maxLength": 254,
      +  "pattern": "^[^\\s@]+@[^\\s@]+\\.[^\\s@]+$",
      +  "type": "string"
      +}
    • addedInput schema / properties / input_files
      Added value: +{
      +  "description": "HTTPS URLs of input files, for example photos, a sketch, a CAD model (STEP, STL), a PDF drawing, or other instructions, or attach the files to the e-mail. At most 20, each at most 2000 characters.",
      +  "items": {
      +    "maxLength": 2000,
      +    "pattern": "^https://",
      +    "type": "string"
      +  },
      +  "maxItems": 20,
      +  "type": "array"
      +}
    • addedInput schema / properties / name
      Added value: +{
      +  "description": "Full name of the person, or registered name of the company, that operates the agent. Optional, but include it whenever you know it (for example from a company name or address already in the conversation) rather than leaving it out or asking the user.",
      +  "maxLength": 200,
      +  "minLength": 1,
      +  "pattern": "^[^\\r\\n]+$",
      +  "type": "string"
      +}
    • addedInput schema / properties / services
      Added value: +{
      +  "description": "Service ids from the service list, if you know them.",
      +  "items": {
      +    "enum": [
      +      "design",
      +      "make",
      +      "assemble",
      +      "measure",
      +      "test",
      +      "verify",
      +      "ship"
      +    ],
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • changedInput schema / properties / task / properties / deliverables / description
      Previous value: -"What you expect to receive (item, files, report, photos, video)."New value: +"What you expect to receive (item, files, report, photos, video). Optional - if you are not sure, leave it out and put it in task.description instead."
    • changedInput schema / properties / task / required
      Previous value: -[
      -  "description",
      -  "deliverables"
      -]New value: +[
      +  "description"
      +]
    • addedInput schema / properties / vat_id
      Added value: +{
      +  "description": "VAT or tax id of the operator, printed on the invoice. Optional.",
      +  "maxLength": 32,
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "task",
      -  "client"
      -]
  6. Changed2 schema fields changed
    • changedInput schema / properties / task / properties / deadline / description
      Previous value: -"Latest acceptable delivery or dispatch date (ISO 8601)."New value: +"Latest acceptable delivery or dispatch date (ISO 8601). Optional; omit if the user gave none."
    • changedInput schema / properties / task / properties / delivery_address / description
      Previous value: -"Required whenever deliverables describes a physical item to be shipped, packed and collected, or handed over in person - omit only for purely digital deliverables (files, a report). One plain string with name, street, city, postcode, country and phone together, in that order; not an object and not a list of lines."New value: +"Required whenever deliverables describes a physical item to be shipped, packed and collected, or handed over in person - omit only for purely digital deliverables (files, a report). One plain string with name, street, city, postcode and country, in that order; add a phone number at the end only if you already have one. Phone is optional - if you already have a name and an address, never stop to ask the user for a phone number. Not an object and not a list of lines."
  7. Changed2 schema fields changed
    • changedInput schema / properties / allow_anonymised_example / description
      Previous value: -"Consent to publish this task as an anonymised example (no names, addresses or personal data), under the confidentiality section of the terms of service. Default false; can be withdrawn."New value: +"Consent to publish this task as an anonymised example (no names, addresses or personal data), under the confidentiality section of the terms of service. Only set true if the client explicitly agreed to this; otherwise omit the field or leave it false. Default false; can be withdrawn."
    • changedInput schema / properties / task / properties / delivery_address / description
      Previous value: -"Name, street, city, postcode, country and phone of the recipient, if something is shipped."New value: +"Required whenever deliverables describes a physical item to be shipped, packed and collected, or handed over in person - omit only for purely digital deliverables (files, a report). One plain string with name, street, city, postcode, country and phone together, in that order; not an object and not a list of lines."
  8. Changed17 schema fields changed
    • addedInput schema / properties / agent / properties / name / maxLength
      Added value: +200
    • changedInput schema / properties / client / properties / country / description
      Previous value: -"Country of the operator, ISO 3166-1 alpha-2."New value: +"Country of the operator, ISO 3166-1 alpha-2 (upper case)."
    • addedInput schema / properties / client / properties / country / pattern
      Added value: +"^[A-Z]{2}$"
    • addedInput schema / properties / client / properties / email / maxLength
      Added value: +254
    • addedInput schema / properties / client / properties / email / pattern
      Added value: +"^[^\\s@]+@[^\\s@]+\\.[^\\s@]+$"
    • addedInput schema / properties / client / properties / name / maxLength
      Added value: +200
    • addedInput schema / properties / client / properties / name / minLength
      Added value: +1
    • addedInput schema / properties / client / properties / name / pattern
      Added value: +"^[^\\r\\n]+$"
    • addedInput schema / properties / client / properties / vat_id / maxLength
      Added value: +32
    • addedInput schema / properties / task / properties / deadline / maxLength
      Added value: +32
    • addedInput schema / properties / task / properties / deliverables / maxLength
      Added value: +5000
    • addedInput schema / properties / task / properties / delivery_address / maxLength
      Added value: +1000
    • addedInput schema / properties / task / properties / description / maxLength
      Added value: +20000
    • changedInput schema / properties / task / properties / input_files / description
      Previous value: -"HTTPS URLs of input files, for example photos, a sketch, a CAD model (STEP, STL), a PDF drawing, or other instructions, or attach the files to the e-mail."New value: +"HTTPS URLs of input files, for example photos, a sketch, a CAD model (STEP, STL), a PDF drawing, or other instructions, or attach the files to the e-mail. At most 20, each at most 2000 characters."
    • addedInput schema / properties / task / properties / input_files / items / maxLength
      Added value: +2000
    • addedInput schema / properties / task / properties / input_files / items / pattern
      Added value: +"^https://"
    • addedInput schema / properties / task / properties / input_files / maxItems
      Added value: +20
  9. Changed1 schema field changed
    • changedInput schema / properties / task / properties / input_files / description
      Previous value: -"HTTPS URLs of input files (STL, STEP, PDF, instructions), or attach the files to the e-mail."New value: +"HTTPS URLs of input files, for example photos, a sketch, a CAD model (STEP, STL), a PDF drawing, or other instructions, or attach the files to the e-mail."
  10. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare the safety profile (mutating, non-idempotent, open-world), and the description adds substantial behavior beyond that: no authentication, the request is non-binding with nothing charged, a human answers within 24 hours every day, and the access_token is 'shown once' as the only key to the quote. That is exactly the kind of context an agent cannot get from annotations.

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 required fields and the non-binding guarantee, then semantics, then return values and the promised turnaround. It is dense and runs long, but nearly every sentence carries operational or parameter guidance; only slight trimming would help.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 13-parameter mutation tool with no output schema, the description covers the return payload (quote_id, access_token, nda_url, upload_url), the response latency, and the auth model. An agent has everything needed to invoke it correctly and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds real meaning on top: delivery_address is flattened into one plain string (recipient, street, postcode, city, country, optional phone last), country is ISO 3166-1 alpha-2, vat_id only what the client provided, and fields are sent flat. Two blind examples further pin the shape.

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 opens with a specific verb+resource ('Creates a request for a fixed-price quote from a human') and immediately scopes it with 'not binding and nothing is charged'. This distinguishes it from siblings like create_task and confirm_delivery, which an agent can tell apart without opening any schema.

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?

It states the required fields and gives a clear conditional rule for delivery_address ('needed when a physical item is shipped, handed over or collected') plus guidance for country and vat_id. It does not explicitly compare against sibling tools or state when NOT to use this tool, so it falls short of a 5.

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