InsumerAPI

Overview Schema Source Related Servers Discussions Admin

Configure merchant NFTs (replaces)

insumer_configure_nfts

DestructiveIdempotent

Set or replace up to four NFT collections a merchant recognizes for holder discounts or recognition only; owner only, whole-number discounts 1–50 with no decimals.

Instructions

Configure the NFT collections a merchant recognizes, each granting a discount or recognition only. Replaces the existing NFT configuration. Max 4 collections. Discounts are whole numbers from 1 to 50; a value with decimals is refused. Owner only.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Merchant ID
`nftCollections`	Yes	NFT collection configurations (0-4)

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	No	true when the API call succeeded
`data`	No	The endpoint's payload: a signed attestation, trust profile, discount, merchant or token records
`keys`	No	JWKS entries (insumer_jwks)
`meta`	No	Response metadata such as version and timestamp
`error`	No	Error details when ok is false
`items`	No	The result when the endpoint returns a JSON array
`message`	No	A plain-text result (insumer_setup), or a message from the API

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv1.17.1Oct 6, 2026

addedInput schema / properties / nftCollections / items / properties / benefitType

Added value: +{
+  "description": "'discount' (the default) grants the discount below. 'recognition' means holders are recognized and no discount is granted.",
+  "enum": [
+    "discount",
+    "recognition"
+  ],
+  "type": "string"
+}

changedInput schema / properties / nftCollections / items / properties / discount / description

Previous value: -"Discount percentage (1-50)"New value: +"Discount percentage: a whole number from 1 to 50, no decimals. Required unless benefitType is 'recognition'."

addedInput schema / properties / nftCollections / items / properties / enabled

Added value: +{
+  "description": "true or false. false keeps the collection in the configuration but switched off. Leave it out for an enabled collection. When re-saving an existing configuration, carry each collection's enabled value through, or a collection that was switched off is switched back on.",
+  "type": "boolean"
+}

changedInput schema / properties / nftCollections / items / properties / taxon / description

Previous value: -"XRPL NFT taxon for filtering by collection. Optional, XRPL only."New value: +"XRPL NFT taxon for filtering by collection: an integer from 0 to 4294967295. Optional, XRPL only."

addedInput schema / properties / nftCollections / items / properties / taxon / maximum
```
Added value: +4294967295
```
addedInput schema / properties / nftCollections / items / properties / taxon / minimum
```
Added value: +0
```

changedInput schema / properties / nftCollections / items / required

Previous value: -[
-  "name",
-  "contractAddress",
-  "chainId",
-  "discount"
-]New value: +[
+  "name",
+  "contractAddress",
+  "chainId"
+]

Changed9 schema fields changedv1.16.0Oct 4, 2026

addedInput schema / properties / id / maxLength
```
Added value: +100
```
addedInput schema / properties / id / minLength
```
Added value: +1
```
addedInput schema / properties / id / pattern
```
Added value: +"^[a-zA-Z0-9_-]+$"
```

changedInput schema / properties / nftCollections / items / properties / chainId / anyOf

Previous value: -[
-  {
-    "enum": [
-      "1",
-      "56",
-      "8453",
-      "43114",
-      "137",
-      "42161",
-      "10",
-      "88888",
-      "1868",
-      "98866",
-      "480",
-      "146",
-      "100",
-      "5000",
-      "534352",
-      "59144",
-      "324",
-      "81457",
-      "42220",
-      "1284",
-      "204",
-      "130",
-      "57073",
-      "1329",
-      "80094",
-      "33139",
-      "167000",
-      "2020",
-      "1285",
-      "88"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "integer"
-  },
-  {
-    "const": "solana",
-    "type": "string"
-  },
-  {
-    "const": "xrpl",
-    "type": "string"
-  },
-  {
-    "const": "bitcoin",
-    "type": "string"
-  }
-]New value: +[
+  {
+    "enum": [
+      "1",
+      "50",
+      "56",
+      "8453",
+      "43114",
+      "137",
+      "42161",
+      "10",
+      "88888",
+      "1868",
+      "98866",
+      "480",
+      "146",
+      "100",
+      "5000",
+      "534352",
+      "59144",
+      "324",
+      "81457",
+      "42220",
+      "204",
+      "130",
+      "57073",
+      "1329",
+      "80094",
+      "33139",
+      "4663",
+      "167000",
+      "2020",
+      "88",
+      "5042"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "integer"
+  },
+  {
+    "const": "solana",
+    "type": "string"
+  },
+  {
+    "const": "xrpl",
+    "type": "string"
+  }
+]

changedInput schema / properties / nftCollections / items / properties / chainId / description

Previous value: -"Onboarding chain: any supported EVM chain ID (1, 56, 8453, 43114, 137, 42161, 10, 146, 100, 5000, 534352, 59144, 324, 81457, 42220, 1284, 204, 130, 57073, 1329, 80094, 33139, 88888, 1868, 98866, 480, 167000, 2020, 1285, 88), 'solana', 'xrpl', or 'bitcoin'"New value: +"Merchant onboarding chain: one of the EVM chain IDs listed in this schema, 'solana', or 'xrpl'. Merchant token and NFT configs are not available on Bitcoin, Tron, Stellar or Sui."

addedInput schema / properties / nftCollections / items / properties / contractAddress / maxLength
```
Added value: +200
```
addedInput schema / properties / nftCollections / items / properties / contractAddress / minLength
```
Added value: +1
```
addedInput schema / properties / nftCollections / items / properties / contractAddress / pattern
```
Added value: +"^[A-Za-z0-9:_]+$"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "data": {
+      "description": "The endpoint's payload: a signed attestation, trust profile, discount, merchant or token records"
+    },
+    "error": {
+      "description": "Error details when ok is false"
+    },
+    "items": {
+      "description": "The result when the endpoint returns a JSON array",
+      "items": {},
+      "type": "array"
+    },
+    "keys": {
+      "description": "JWKS entries (insumer_jwks)",
+      "items": {},
+      "type": "array"
+    },
+    "message": {
+      "description": "A plain-text result (insumer_setup), or a message from the API"
+    },
+    "meta": {
+      "description": "Response metadata such as version and timestamp"
+    },
+    "ok": {
+      "description": "true when the API call succeeded",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

Addedv0.1.0Apr 28, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, so the replace semantics are partly carried by structured data. The description still adds substantive context: the 4-collection cap, that 'recognition' grants no discount, that decimal discounts are refused, and that the caller must be the owner. It stops short of describing what happens to previously configured collections beyond the replacement.

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?

Four short sentences, front-loaded with the core action and the destructive replace behavior. Every sentence carries a distinct constraint (scope, replace, cap, validation, authorization) with no filler.

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 return values need no explanation, and the annotations cover the safety profile. The description completes the picture with permission requirements, cardinality limits, and value validation. Minor gaps remain around failure modes and whether omitted collections are deleted outright.

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 100%, so both top-level parameters and all nested fields are already documented in the schema, including the discount 1-50 range, taxon, chainId enum, and enabled carry-through rule. The description restates the discount integer constraint and the 4-item cap but adds no format or syntax detail beyond the schema, making the baseline 3 appropriate.

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 and resource ('Configure the NFT collections a merchant recognizes') and immediately quantifies scope (max 4, discount-or-recognition only). It is distinguishable from the sibling insumer_configure_tokens by naming NFTs explicitly, though no sibling is called out by name.

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

Usage Guidelines3/5

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

The description establishes the key operational fact that this is a replace, not an append ('Replaces the existing NFT configuration'), and states 'Owner only'. It does not, however, say when to choose this tool over insumer_configure_tokens or insumer_configure_settings, nor does it give explicit when-not conditions.

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