catalog

Request a quotation

get_quote

Request a formal quotation for catalog parts. Creates a quote request and returns its reference; Satmarin replies within one working day. This call emails nothing to the requester.

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": {
      "items": "<items>",
      "contact": "<contact>"
    },
    "name": "get_quote"
  }
}

Input Schema

Name	Required	Description
`items`	Yes	1 to 20 lines. Every part number must be a live, quotable catalog product.
`notes`	No	Optional free text, up to 1000 characters.
`contact`	Yes

Output Schema

Name	Required	Description	Default
`status`	Yes
`message`	Yes
`reference`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 16, 2026

addedInput schema / properties / contact / properties / billing_address

Added value: +{
+  "description": "Optional postal billing address, used only if a proforma invoice is later issued. Free text, newline separated, at most 6 lines and 300 characters. Markup is removed. The country comes from contact.country, not from this field.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed1 schema field changedOct 15, 2026

addedInput schema / properties / contact / properties / vat

Added value: +{
+  "description": "Optional VAT or tax registration number, e.g. BE0479944518. Letters and digits only, up to 32 characters; spaces, dots and dashes are removed. Not validated against any tax register.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed1 schema field changedOct 15, 2026

addedInput schema / properties / contact / properties / country

Added value: +{
+  "description": "Optional ISO 3166-1 alpha-2 country code of the customer, e.g. BE. Case-insensitive. Used for shipping and VAT treatment on the quotation.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed1 schema field changedSep 14, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "message": {
+      "type": "string"
+    },
+    "reference": {
+      "type": "string"
+    },
+    "status": {
+      "enum": [
+        "received"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "reference",
+    "status",
+    "message"
+  ],
+  "type": "object"
+}

First observedSep 12, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description is consistent with those. Beyond the annotations it adds real behavioral value: the tool returns a reference and Satmarin responds within one working day, and critically that no email is sent to the requester despite it being a request-style call.

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?

Two short sentences, front-loaded with the core action and outcome. The closing email disclaimer earns its place by pre-empting a common assumption about 'request' calls, though the sentence is slightly clipped in phrasing.

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?

An output schema exists, so the return value need not be detailed, and the annotations carry the safety profile for this non-destructive write. Combined with a 67%-documented nested schema, the description covers the remaining gaps (SLA, no-email side effect) adequately, leaving only minor unanswered questions about error/validation behavior.

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 67%, so most parameters (items, qty, sku, notes, contact fields, vat, country, billing_address) are already documented in the schema, which sets the baseline at 3. The description adds nothing about parameter formats or constraints beyond the vague phrase 'catalog parts', so it neither compensates for the uncovered fields nor drops below baseline.

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?

The description names a specific verb and resource ('Request a formal quotation... Creates a quote request and returns its reference') and scopes it to 'catalog parts'. An agent can immediately tell this is a write-side quoting operation, though it never contrasts itself with siblings like search_parts or check_compatibility.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no statement of when to choose this tool over the siblings or what prerequisites apply (e.g. parts must first be found via search_parts). The only usage signal is the phrase 'for catalog parts', which is implied scope rather than guidance.

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

All catalog tools Inspect

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

Need Help?