25karats — Made-to-Order Wedding & Engagement Rings

browse_collection

Read-onlyIdempotent

Browse one collection/category page deterministically — the same product set, ordering, and filters a shopper sees on the site. Pass the collection permalink from list_collections (e.g. 'wedding-rings/womens/eternity'). Filter by style tags, metals, or sort; paginate 24 per page. Prefer search_products for free-text intent and this tool for "show me everything in X".

Input Schema

TableJSON Schema

Name	Required	Description
`cats`	No	Child-category slugs on a listing-nav collection; matches the site's cats filter
`page`	No
`sort`	No	Default: best sellers
`tags`	No	Style tag slugs, e.g. ['celtic','braided']
`limit`	No	Max 24
`metals`	No	Offered metal codes, e.g. ['14K','PLAT']; price and URL use the first offered selection
`price_tag`	No	Price-range slug or id, e.g. '501-1000'; accepts one value or an array
`collection`	Yes	Collection permalink, with or without leading slash

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	No
`page`	No
`per_page`	No
`products`	No
`collection`	Yes
`total_count`	No
`applied_filters`	No
`child_collections`	No

TDQS

A4.6/5.0

Behavior4/5

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

The description adds value beyond annotations by specifying determinism ('the same product set, ordering, and filters a shopper sees'), pagination ('24 per page'), and the need for a permalink. Annotations already declare readOnly and idempotent hints, and the description complements these without contradiction.

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?

The description is two sentences, front-loaded with purpose and key behaviors, then usage guidance. Every sentence contributes meaning without redundancy, making it concise and well-structured.

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?

Given the tool's complexity (8 parameters, but only 1 required) and the presence of an output schema and good annotations, the description covers essential aspects: function, inputs needed, pagination, and alternatives. It does not explicitly mention error handling or edge cases, but these are not critical for tool selection or 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?

Schema coverage is high (88%), and the description supplements by explaining that the collection permalink comes from list_collections with an example, and notes that metals' 'price and URL use the first offered selection'—details not fully captured in the schema.

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 clearly states the tool's purpose: 'Browse one collection/category page deterministically' with specific details about the product set, ordering, and filters. It explicitly contrasts with search_products, distinguishing it from the sibling tool and conveying a specific use case.

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

Usage Guidelines5/5

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

Provides explicit guidance on when to use this tool vs. search_products ('Prefer search_products for free-text intent and this tool for "show me everything in X"') and references list_collections for obtaining the permalink, giving clear context and exclusions.

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

All 25karats — Made-to-Order Wedding & Engagement Rings tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: browse_collection is for deterministic category browsing while search_products is for free-text discovery, and get_product, get_product_images, and price_product each cover a separate aspect of product research. The diamond search is also cleanly separated from catalog product search.

Naming Consistency5/5

All eight tools follow a consistent snake_case verb_noun pattern: browse_, get_, list_, price_, and search_. Any variability is purely semantic (e.g., list_collections vs browse_collection) rather than a style mismatch.

Tool Count5/5

Eight tools is well-scoped for a made-to-order jewelry e-commerce assistant: taxonomy, product search/browse, product detail, images, pricing, diamond inventory, and store policy information are all covered without redundant or unnecessary tools.

Completeness5/5

The tool set covers the full shopper journey: discover collections, search products, inspect product details and images, configure and price a product, research diamonds, and find store policies. The deep_link_url from price_product provides an effective handoff to checkout, eliminating any hard dead end.

Resources

Need Help?