Skip to main content
Glama

Get a lab report-check link

check_report
Read-onlyIdempotent

Returns the web address of the grading laboratory's own report-check page for a GIA or IGI report number, after checking that the number has that laboratory's format. Use this when the user wants to verify a diamond's grading report themselves. Limits: it only builds the link; it does not open, read or confirm the report, and only GIA and IGI are supported. For an IGI number starting with LG it also notes that such reports are normally for lab-grown diamonds.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lab": "<lab>",
      "report_number": "<report_number>"
    },
    "name": "check_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
labYesThe laboratory that issued the report.
report_numberYesThe report number printed on the report (GIA: 7–10 digits; IGI: 7–10 digits, lab-grown reports may start with LG).

Output Schema

NameRequiredDescriptionDefault
labYes
noteNoA reading tip about the number's format; the report itself is the authority.
report_numberYes
report_check_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the format-validation gate that precedes link construction, the hard limit that it does not open or confirm the report, and the domain restriction to GIA/IGI only. It does not say what happens on a format mismatch (error vs. empty result), which is the one behavioral gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the core action, then usage trigger, then limits. Efficient overall, though the trailing LG sentence duplicates information already carried by the schema and could be trimmed.

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?

With an output schema present, the return value need not be explained, and annotations cover the safety profile; the description supplies the validation gate, scope restrictions and domain limits. Complete enough to call correctly, with only the invalid-format failure mode left unspecified.

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 coverage is 100%, so both parameters, the enum and the LG/lab-grown nuance are already documented in the schema itself. The description's LG sentence largely restates what the report_number field description already says, adding little beyond the baseline.

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 and resource: 'Returns the web address of the grading laboratory's own report-check page' for a GIA or IGI report number, gated on format validation. The LIMITS clause ('only builds the link; it does not open, read or confirm the report') sharply bounds the scope so an agent can tell it apart from report-retrieval tools like get_diamond.

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?

'Use this when the user wants to verify a diamond's grading report themselves' gives an explicit trigger condition, and the limits sentence functions as a when-not by ruling out reading or confirming the report. It stops short of naming an alternative sibling tool to use instead when the agent needs actual report contents.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources