Skip to main content
Glama

AirShelf Catalog

by ai.airshelf
OverviewDiscussionsAdmin

Request a quote from a merchant

request_quote
Destructive

Send a quote request for catalog products to a merchant's sales team on behalf of a named buyer.

This is a two-step, double opt-in flow. The first call emails a confirmation link to contact.email and returns status "confirmation_required"; no lead exists and no merchant is contacted until the buyer confirms. A later call with the same arguments reports "awaiting_confirmation" while the email is unconfirmed, or "received" with a reference_number after confirmation.

Merchant slugs come from list_merchants. Network-catalog brands that are absent from that list use merchant:"airshelf-network" with brandSlug:""; AirShelf routes the confirmed request to that brand.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNoAny extra context from the buyer
contactYesBuyer contact details
merchantYesMerchant slug or id (from list_merchants), or "airshelf-network" for network-catalog brands
productsNoCatalog slugs the buyer is interested in; may be omitted when attaching contact to a rep desk reference
quantityNoUnits the buyer wants
brandSlugNoManufacturer slug (from search results) — required with merchant:"airshelf-network" so the lead reaches the right brand
referenceNoRep desk trace returned by ask, so confirmed contact reaches the same request

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNo
next_stepNo
reference_numberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / products / default
      Added value: +[]
    • changedInput schema / properties / products / description
      Previous value: -"Catalog slugs the buyer is interested in"New value: +"Catalog slugs the buyer is interested in; may be omitted when attaching contact to a rep desk reference"
    • removedInput schema / properties / products / minItems
      Removed value: -1
    • addedInput schema / properties / reference
      Added value: +{
+  "description": "Rep desk trace returned by ask, so confirmed contact reaches the same request",
+  "pattern": "^REQ-[A-Z0-9-]{1,4}-[A-Z0-9]{6}$",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "merchant",
-  "products",
-  "contact"
-]New value: +[
+  "merchant",
+  "contact"
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / brandSlug / minLength
      Added value: +1
  3. Changed2 schema fields changed
    • addedInput schema / properties / merchant / minLength
      Added value: +1
    • addedInput schema / properties / products / items / minLength
      Added value: +1
  4. Changed2 schema fields changed
    • addedInput schema / properties / brandSlug
      Added value: +{
+  "description": "Manufacturer slug (from search results) — required with merchant:\"airshelf-network\" so the lead reaches the right brand",
+  "type": "string"
+}
    • changedInput schema / properties / merchant / description
      Previous value: -"Merchant slug or id (from list_merchants)"New value: +"Merchant slug or id (from list_merchants), or \"airshelf-network\" for network-catalog brands"
  5. Changed4 schema fields changed
    • removedOutput schema / properties / merchant
      Removed value: -{
-  "type": "string"
-}
    • addedOutput schema / properties / next_step
      Added value: +{
+  "type": "string"
+}
    • removedOutput schema / properties / referenceNumber
      Removed value: -{
-  "description": "Quote reference for the buyer",
-  "type": "string"
-}
    • addedOutput schema / properties / reference_number
      Added value: +{
+  "type": "string"
+}
  6. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "merchant": {
+      "type": "string"
+    },
+    "referenceNumber": {
+      "description": "Quote reference for the buyer",
+      "type": "string"
+    },
+    "status": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  7. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only flag it as a non-read-only, open-world, destructive write. The description adds substantial context beyond that: the double opt-in flow, that no lead exists and no merchant is contacted until confirmation, and the exact status strings ("confirmation_required", "awaiting_confirmation", "received") plus the reference_number returned. This is exactly the extra behavioral detail annotations cannot convey.

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?

Three tight paragraphs, front-loaded with purpose followed by flow and edge-case routing. Every sentence carries information, though the density is high and could be marginally trimmed.

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 7-parameter tool with nested objects and an output schema, the description covers the flow, status states, required identifier sourcing, and the network-brand edge case. Since an output schema exists, return values need not be explained, and nothing an agent needs to call it correctly is missing.

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 baseline is 3. The description adds real meaning beyond the schema by explaining the merchant/brandSlug relationship for airshelf-network and clarifying the merchant slug source, though it does not elaborate on reference, quantity, or products syntax.

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, resource and actor: 'Send a quote request for catalog products to a merchant's sales team on behalf of a named buyer.' It is clearly distinct from the read-oriented siblings (find_products, get_product, list_merchants) and references list_merchants as the source of merchant slugs.

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 conditional guidance: merchant slugs come from list_merchants, and network-catalog brands absent from that list must use merchant:"airshelf-network" with brandSlug. It also explains the two-step opt-in sequence. It stops short of stating when NOT to use this tool versus an alternative, so it does not reach a 5.

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

All AirShelf Catalog toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources