Skip to main content
Glama

Submit B2B Inquiry

submit_b2b_inquiry
Destructive

Product lookups record channel labels and returned product codes for Cigo's usage analytics. The optional journey_token is a server-issued correlation value linking lookups and a later inquiry in the same customer conversation. Omission starts a new lookup journey. Save a customer-confirmed quote, sample or supply-feasibility inquiry (not an order). For filter media or nanofiber roll material requests, collect intended use, requested width/thickness if known, quantity and desired schedule; unknown specifications may be discussed with staff. Do not promise a price, custom manufacturing capability or certification before review. Accept B2B inquiries from any country in the customer's language for HVAC/cleanroom filters, nanofiber materials, waterproof/breathable textiles, cosmetic applications and other uses. Ask for company, contact email, destination country, subject and details; preserve original text and pass the customer's language code. Before submitting, show the inquiry and obtain confirmation. Explain that Cigo stores the original and, when enabled, sends the subject and details to Microsoft Azure Translator for Korean machine translation. When enabled, saving an inquiry also sends a notification email to Cigo's fixed operator address; a sent email cannot be recalled. Do not send passwords or payment data. Inquiry acceptance does not establish overseas sales or shipping availability. Supply feasibility, price, certification and delivery are subject to staff review. 전 세계 B2B 문의 접수: 공조·클린룸 필터, 나노섬유 원단 및 다양한 응용 소재.

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": {
      "company_name": "<company_name>",
      "manager_name": "<manager_name>",
      "contact_info": "<contact_info>",
      "inquiry_details": "<inquiry_details>"
    },
    "name": "submit_b2b_inquiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNo
languageNoko
quantityNo
company_nameYes
contact_infoYes
manager_nameYes
contact_emailNo
contact_phoneNo
journey_tokenNo
specificationsNo
inquiry_detailsYes
inquiry_subjectNo
inquiry_categoryNoother

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / journey_token
      Added value: +{
      +  "default": "",
      +  "type": "string"
      +}
  2. Changed8 schema fields changed
    • addedInput schema / properties / contact_email
      Added value: +{
      +  "default": "",
      +  "type": "string"
      +}
    • addedInput schema / properties / contact_phone
      Added value: +{
      +  "default": "",
      +  "type": "string"
      +}
    • addedInput schema / properties / country
      Added value: +{
      +  "default": "",
      +  "type": "string"
      +}
    • addedInput schema / properties / inquiry_category
      Added value: +{
      +  "default": "other",
      +  "type": "string"
      +}
    • addedInput schema / properties / inquiry_subject
      Added value: +{
      +  "default": "",
      +  "type": "string"
      +}
    • addedInput schema / properties / language
      Added value: +{
      +  "default": "ko",
      +  "type": "string"
      +}
    • addedInput schema / properties / quantity
      Added value: +{
      +  "default": "",
      +  "type": "string"
      +}
    • addedInput schema / properties / specifications
      Added value: +{
      +  "default": "",
      +  "type": "string"
      +}
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag non-read-only, destructive and open-world behavior, and the description adds meaningful context beyond them: the original text is stored, subject and details may be sent to Microsoft Azure Translator for Korean machine translation, a notification email goes to a fixed operator address, and a sent email cannot be recalled. Those are exactly the side effects an agent needs to warn a customer about; it stops short of describing what data retention or reversibility looks like beyond the email.

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

Conciseness3/5

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

Every sentence carries policy content, but the paragraph is poorly front-loaded, opening on analytics metadata and journey tokens before the actual purpose, and it closes with a Korean sentence that largely repeats the scope statement. The result is dense and hard to scan for the single most important fact: what this tool saves.

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 13-parameter, non-read-only tool with no output schema and no schema descriptions, the definition covers compliance, data sharing, confirmation workflow, prohibited content and per-parameter intent well. Remaining gaps are the three undocumented parameters and any statement about what the tool returns on success or failure.

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?

With 0% schema description coverage across 13 parameters, the description carries the burden and does so for most of them: journey_token (server-issued correlation value, omission starts a new journey), language (pass the customer's language code), quantity, specifications (width/thickness), company, contact email, destination country, subject and details. The gaps are manager_name, contact_phone and inquiry_category, including its default of "other", which are never explained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The actual purpose is stated only in the third sentence ("Save a customer-confirmed quote, sample or supply-feasibility inquiry (not an order)"), while the opening sentences describe product-lookup analytics and journey_token correlation, which belong to a different operation. An agent must read past misleading lead content to learn it is a submission tool, and no sibling is named for differentiation beyond the vague "not an order".

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?

Guidance is unusually concrete: collect intended use, width/thickness, quantity and schedule, show the inquiry for confirmation before submitting, never promise price or certification, and do not send passwords or payment data. What is missing is any routing guidance versus named siblings such as prepare_carsafe_purchase or get_hvac_filter_info, so the agent gets rich workflow rules but no explicit alternative selection.

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