Ada Diamonds

Search engagement ring settings

search_engagement_rings

Read-only

Search Ada Diamonds' engagement ring settings by center-stone shape, style, and setting price. Setting prices exclude the center diamond — pair with search_diamonds to quote a complete ring. MCP Apps-enabled: hosts that support MCP Apps render the results as an interactive card grid.

Input Schema

Name	Required	Description
`q`	No	Free text, e.g. "east west bezel"; typo tolerant, best match first
`type`	No	Setting type, e.g. Solitaire, Halo, Three Stone
`limit`	No	Maximum number of results to return, 1 to 50 (default 10)
`shape`	No	Center-stone shape the setting must accommodate, e.g. Oval
`style`	No	Design style, e.g. Petite Four Prong, Trellis, Bezel
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`llm_model`	Yes	The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
`max_price`	No	Maximum setting price in US dollars, excluding the center diamond
`min_price`	No	Minimum setting price in US dollars, excluding the center diamond
`conversation_id`	No	Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

Output Schema

Name	Required	Description
`kind`	Yes	Which catalog the results come from
`items`	Yes	The matching entries, best match first
`query`	Yes	The filters that were applied (only the ones you sent)
`shown`	Yes	How many entries are in `items`
`total`	Yes	How many catalog entries matched before the limit
`browseUrl`	Yes	Web page listing the full catalog for this search

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

changedInput schema / properties / conversation_id / description

Previous value: -"Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it."New value: +"Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request."

Changed9 schema fields changedOct 23, 2026

changedOutput schema / properties / items / items / properties / image / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "alt": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "description": "Alt text, when the catalog has one"
-      },
-      "url": {
-        "description": "Image URL on the Ada Diamonds CDN",
-        "type": "string"
-      }
-    },
-    "required": [
-      "url",
-      "alt"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "alt": {
+        "description": "Alt text, when the catalog has one",
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "url": {
+        "description": "Image URL on the Ada Diamonds CDN",
+        "type": "string"
+      }
+    },
+    "required": [
+      "url",
+      "alt"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / items / items / properties / platinumUpcharge / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
addedOutput schema / properties / items / items / properties / platinumUpcharge / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / items / items / properties / priceFrom / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / items / items / properties / priceFrom / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / items / items / properties / style / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / items / items / properties / style / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / items / items / properties / type / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / items / items / properties / type / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed1 schema field changedOct 23, 2026

changedInput schema / properties / q / description

Previous value: -"Free-text match on the setting name"New value: +"Free text, e.g. \"east west bezel\"; typo tolerant, best match first"

Changed5 schema fields changedSep 18, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / context

Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}

addedInput schema / properties / conversation_id

Added value: +{
+  "description": "Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.",
+  "type": "string"
+}

addedInput schema / properties / llm_model

Added value: +{
+  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
+  "type": "string"
+}

addedInput schema / required

Added value: +[
+  "context",
+  "llm_model"
+]

Changed1 schema field changedSep 2, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedSep 1, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds context the annotations do not: that prices exclude the center diamond and that MCP Apps hosts render results as an interactive card grid, which meaningfully changes how an agent should interpret and present output. Pagination/limit behavior is left to the schema.

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?

Three tight sentences with zero waste: purpose first, then the pricing caveat and sibling pairing, then the rendering behavior. Each sentence carries distinct, actionable information and the most important constraint is front-loaded.

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?

With an output schema present, annotations covering the safety profile, and 100% schema description coverage, the description supplies everything an agent needs: what it searches, how price is scoped, which sibling completes the task, and how results render. No gaps remain for a 10-parameter read-only search.

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 every parameter is already documented in the schema, including the price-exclusion semantics for min_price/max_price and the conversation_id workflow. The description's price note largely restates what the schema says, adding no new per-parameter syntax or constraints, so the baseline 3 applies.

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 (Search), a specific resource (engagement ring settings), and the three filter dimensions (shape, style, price). It also explicitly distinguishes the tool from search_diamonds by noting the setting price excludes the center diamond, so an agent can tell the siblings apart from the description alone.

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?

Explicitly says to pair with search_diamonds to quote a complete ring, which routes the agent to the complementary tool and clarifies scope. It stops short of an explicit when-not-to-use condition against other siblings like search_jewelry or search_knowledge_base, so it is strong but not fully exhaustive.

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

All Ada Diamonds 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?