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

TableJSON Schema

Name	Required	Description
`q`	No	Free-text match on the setting name
`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	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.

Output Schema

TableJSON 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.

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.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds useful private behavior: results are setting-only with prices excluding diamonds, and rendering may become an interactive card grid in MCP Apps-enabled hosts. No contradiction with annotations.

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 sentences, each earning its place: purpose and filters, price-scope caveat with sibling pairing, and the MCP Apps rendering note. The core action is front-loaded with no filler or redundancy.

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?

For a 10-parameter tool, the description covers the key domain decision logic (settings vs. complete ring, pairing with search_diamonds) while the full schema documents every parameter and an output schema exists. The only minor gap is no guidance on the analytics-only parameters (context, llm_model), but those are fully described in the schema.

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 the baseline is 3. The description additionally clarifies that min_price and max_price values exclude the center diamond, which is meaningful domain semantics beyond the raw schema text, and it ties shape/style/price to the search behavior.

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?

The description opens with a specific verb and resource, "Search Ada Diamonds' engagement ring settings," and enumerates the filter dimensions (shape, style, price), immediately distinguishing it from sibling tools like search_diamonds and search_jewelry. It clearly identifies this as the settings-specific search, not a general jewelry query.

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?

The description gives concrete usage context: settings prices exclude the center diamond and should be paired with search_diamonds for a complete ring quote. It does not explicitly state when not to use this tool or name alternative searches by condition, but the pairing guidance and scope are enough for an agent to route correctly.

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?