dutch_marquise_definitionThe published definition of the Dutch Marquise diamond cut: geometry, certificate wording, and typical length to width ratio. A Dutch Marquise is an elongated hexagonal cut diamond.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already mark the tool as read-only, idempotent, and non-destructive. The description adds value by specifying the kind of information returned (geometry, certificate wording, typical length-to-width ratio) and by clarifying that a Dutch Marquise is an elongated hexagonal cut, which helps set expectations for the tool's output without weakening the safety profile.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences carry the core definition, the content details, and the classification example with no filler. The most distinctive identifying phrase is front-loaded and the supporting details are compact.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter, read-only reference with no output schema, the description gives enough content detail for an agent to decide whether this tool answers a query about Dutch Marquise cut definitions. It is not exhaustive—e.g., it does not mention source publication or format—but nothing essential for invocation is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, making detailed parameter documentation unnecessary. The empty input schema is fully consistent with a static definition-lookup tool, and the description does not invent parameters or leave any input ambiguity.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description identifies a specific resource—the published definition of the Dutch Marquise cut—and lists concrete content: geometry, certificate wording, and length-to-width ratio. It does not use an explicit verb like 'returns' or 'describes,' and its relationship to the sibling 'define' tool is not directly clarified, though the specialist scope is clear.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance is given about when to call this tool instead of define, search_encyclopedia, or about_stienhardt. The intended use is only implied by the name and content hints, and there is no mention of the conditions that would make a sibling tool preferable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools target clearly distinct actions: searching, fetching details, looking up terms, verifying reports. The main ambiguity is between define and dutch_marquise_definition, since the latter appears to be a single encyclopedia entry surfaced as a standalone tool.
All names are snake_case and readable, but the set mixes verb-led names like search_inventory and get_product with noun-phrase names like lab_grown_price_index and dutch_marquise_definition. The pattern is not consistent enough to predict the tool name from the action alone.
Ten tools is well within the ideal range for a server that handles both diamond education and catalog shopping. Each tool contributes to a clear workflow: learn about diamonds, search inventory, fetch product details, and verify grading reports.
The tool surface covers the main user journey: research terms, search inventory, get product detail, understand grading, and verify reports. Minor gaps exist, such as only having a dedicated definition for the Dutch Marquise cut while other shapes rely on the general encyclopedia lookup.