Skip to main content
Glama
Sign In

kalicart-global

by io.github.giuseppesocci-bot
OverviewDiscussionsAdmin

Verify constraints on one offer (true / false / unknown)

verify_offer
Read-onlyIdempotent

Checks ONE offer (optionally a selected variant) and returns true, false or unknown per constraint with evidence. Pass constraints as an ARRAY, for example [{"field":"available"},{"field":"price","max":300,"currency":"EUR"},{"field":"ships_to","value":"IT:CB"}]. available has no expected key: ask for the fact and read its result. For a merchant-declared variant option use {"field":"option","keys":["pa_color"],"values":["black"]}; use only native merchant values, with variation_id for a specific variant. Nothing is inferred or translated. Results are unknown outside max_age_seconds (default 86400); live=true reads the merchant now. Checkout is the final authority.

Input Schema

NameRequiredDescriptionDefault
liveNotrue reads the merchant Bridge now (one request).
p2209_idYesOffer id from global_search (e.g. prod_duinshop-it_446678).
constraintsYesRequired array of 1-8 objects. Each object has field and only the keys shown by its schema. Examples: [{"field":"available"}], [{"field":"price","max":50,"currency":"EUR"}].
variation_idNoVariant to check (from matching_variants or variants_compact). Without it, variant-dependent constraints may be unknown.
max_age_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / constraints / description
      Previous value: -"Up to 8 constraints, e.g. [{\"field\":\"price\",\"max\":50},{\"field\":\"available\"},{\"field\":\"ships_to\",\"value\":\"IT:CB\"}]."New value: +"Required array of 1-8 objects. Each object has field and only the keys shown by its schema. Examples: [{\"field\":\"available\"}], [{\"field\":\"price\",\"max\":50,\"currency\":\"EUR\"}]."
    • removedInput schema / properties / constraints / items / additionalProperties
      Removed value: -{}
    • addedInput schema / properties / constraints / items / anyOf
      Added value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "currency": {
+        "pattern": "^[A-Z]{3}$",
+        "type": "string"
+      },
+      "field": {
+        "const": "price",
+        "type": "string"
+      },
+      "max": {
+        "minimum": 0,
+        "type": "number"
+      },
+      "min": {
+        "minimum": 0,
+        "type": "number"
+      }
+    },
+    "required": [
+      "field"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "field": {
+        "const": "available",
+        "type": "string"
+      }
+    },
+    "required": [
+      "field"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "field": {
+        "const": "option",
+        "type": "string"
+      },
+      "keys": {
+        "items": {
+          "minLength": 1,
+          "type": "string"
+        },
+        "maxItems": 16,
+        "type": "array"
+      },
+      "values": {
+        "items": {
+          "minLength": 1,
+          "type": "string"
+        },
+        "maxItems": 32,
+        "minItems": 1,
+        "type": "array"
+      }
+    },
+    "required": [
+      "field",
+      "values"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "field": {
+        "const": "brand",
+        "type": "string"
+      },
+      "values": {
+        "$ref": "#/properties/constraints/items/anyOf/2/properties/values"
+      }
+    },
+    "required": [
+      "field",
+      "values"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "field": {
+        "const": "merchant",
+        "type": "string"
+      },
+      "values": {
+        "$ref": "#/properties/constraints/items/anyOf/2/properties/values"
+      }
+    },
+    "required": [
+      "field",
+      "values"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "field": {
+        "const": "attribute",
+        "type": "string"
+      },
+      "keys": {
+        "$ref": "#/properties/constraints/items/anyOf/2/properties/keys"
+      },
+      "values": {
+        "$ref": "#/properties/constraints/items/anyOf/2/properties/values"
+      }
+    },
+    "required": [
+      "field",
+      "values"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "field": {
+        "const": "barcode",
+        "type": "string"
+      },
+      "values": {
+        "$ref": "#/properties/constraints/items/anyOf/2/properties/values"
+      }
+    },
+    "required": [
+      "field",
+      "values"
+    ],
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "field": {
+        "const": "ships_to",
+        "type": "string"
+      },
+      "value": {
+        "pattern": "^[A-Z]{2}(:[A-Z0-9-]{1,10})?$",
+        "type": "string"
+      }
+    },
+    "required": [
+      "field",
+      "value"
+    ],
+    "type": "object"
+  }
+]
    • removedInput schema / properties / constraints / items / type
      Removed value: -"object"
  2. Added

TDQS

A4.3/5.0
Behavior5/5

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

Beyond annotations (readOnly/idempotent/non-destructive/openWorld), it discloses freshness semantics (unknown outside max_age_seconds, default 86400; live=true issues one merchant request) and the no-inference/no-translation rule. These are real behavioral traits an agent must know before trusting a result.

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 core purpose and return contract, then parameter-shape examples. Dense but each sentence carries information; slightly run-on in the middle clause.

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?

No output schema exists, and the description compensates by explaining the return contract (per-constraint verdict plus evidence) and the 'unknown' fallback. Given the 8-branch constraint union, this is sufficient for correct invocation.

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 80% schema coverage the baseline is 3, but the description adds genuine meaning: 'available' takes no expected key, 'option' uses merchant-native keys/values, and variation_id's effect on variant-dependent constraints. Only max_age_seconds' default is left to the description alone.

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?

States a specific verb ('Checks') and resource ('ONE offer'), plus the return shape (true/false/unknown per constraint with evidence). The 'ONE offer' scoping implicitly separates it from verify_basket, but no sibling is named explicitly.

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 concrete usage rules: constraints must be an array, native merchant values only, live=true for a fresh read, variation_id for a specific variant, and 'Checkout is the final authority'. It doesn't explicitly state when to prefer this over verify_basket or get_offer_attestation.

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

All kalicart-global 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