Skip to main content
Glama

Submit an export inquiry

submit_export_inquiry
Idempotent

Send an agricultural export inquiry (price, quantity, destination, Incoterm) to Barmaan's export sales team, same inbox as the website export form. Ask the user for name and phone or email first and do not invent contact details. Call once with confirm=false to get a preview, show it to the user, then call with confirm=true after they agree.

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": {
      "name": "<name>"
    },
    "name": "submit_export_inquiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesImporter contact name, asked from the user (not guessed).
emailNoContact email. Phone or email is required.
phoneNoContact phone/WhatsApp with country code. Phone or email is required.
localeNoContent language: en, fa, ar or ckb.en
companyNo
confirmNofalse = preview only, nothing is sent. Set true only after the user explicitly agreed to send these details to Barmaan.
countryNoImporter country.
messageNoAnything else the importer wants to say.
productNoExport product slug from the Barmaan export catalog. Omit for the default product.
incotermNoPreferred Incoterm.
quantityNoFree text such as '2 tons per week'.
destinationNoDestination port/city/country.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, but the description adds genuinely non-obvious behavior: the two-phase preview/send flow, that confirm=false sends nothing, and that the message lands in the same inbox as the website export form. It does not describe failures, rate limits, or what the preview payload looks like.

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?

Three sentences, front-loaded with purpose, then the contact-data rule, then the confirm workflow in call order. Every clause carries an actionable instruction and nothing is padded.

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 12-parameter write tool with no output schema, the description covers the essentials: what gets sent, who receives it, and the safety workflow. The remaining gap is that it never says what the preview or the confirmed call returns (e.g., a reference ID), which matters for telling the user the inquiry was logged.

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

Parameters5/5

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

Schema coverage is 92%, so the baseline would be 3, but the description adds meaning the schema cannot express: name and phone-or-email must be elicited from the user rather than fabricated, and the key inquiry fields (price/quantity/destination/Incoterm) are grouped as the substantive content. That is real semantic guidance beyond the field descriptions.

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 (send) and resource (agricultural export inquiry) plus the fields it carries (price, quantity, destination, Incoterm) and the destination (Barmaan's export sales team). An agent immediately knows what this does and that it produces an outbound human-facing message, not a read.

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 strong procedural guidance: collect name plus phone or email from the user, never invent contact details, preview with confirm=false, then confirm=true only after the user agrees. It does not, however, distinguish this from the sibling request_quote, so an agent could be unsure which of the two to pick for a pricing request.

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