Skip to main content
Glama

Reagent label parser

parse_reagent_label
Read-onlyIdempotent

Turn text read from a reagent bottle or kit label (OCR or typed) into structured fields such as product name, catalog number, lot, expiry, concentration and storage. Parses the provided text only; send the label text, not an image.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "parse_reagent_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
ocrTextNoOCR text extracted from a reagent label image. The browser tool performs OCR locally; this endpoint parses provided text only.
ocrConfidenceNoOptional OCR confidence percentage from the OCR engine.
sourceImageNameNoOptional source image file name or identifier for review context.

Output Schema

NameRequiredDescriptionDefault
cardNoWhat the Verbex card draws; same values as the notebook entry.
toolYes
resultNo
humanUrlNo
warningsNo
inputNotesNoHow the input was read when it was not in the documented shape. Tell the user.
safetyNotesNo
toolVersionNo
notebookEntryNoMarkdown entry to paste into a lab notebook.
validationErrorsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / inputNotes
      Added value: +{
      +  "description": "How the input was read when it was not in the documented shape. Tell the user.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. First observed

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, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety and determinism are covered. The description adds the non-obvious behavioral boundary that the endpoint performs no OCR and only parses supplied text, which prevents a common misuse. It does not discuss handling of unparseable or partial label text, which would have pushed this higher.

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?

Two sentences, zero filler, with the core action first and the critical constraint ('send the label text, not an image') placed last as a closing guardrail. Nothing is repeated from the schema or annotations.

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?

An output schema exists, so return values need not be explained, and the input schema fully documents all three parameters. For a stateless, read-only parser, the description supplies everything needed to invoke it correctly, including the input-modality constraint.

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 all three parameters (ocrText, ocrConfidence, sourceImageName) are already documented, including ranges and optionality. The description's field list describes outputs rather than input parameters, so it adds no syntax or format detail beyond the schema. 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 and resource ('Turn text read from a reagent bottle or kit label ... into structured fields') and enumerates the extracted fields (product name, catalog number, lot, expiry, concentration, storage). The scope sentence 'Parses the provided text only' distinguishes it from any OCR/image-handling capability an agent might assume exists.

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?

Gives a clear usage condition and an explicit exclusion: send label text, not an image, and text may come from OCR or be typed. It does not name an alternative tool for the image case, so the agent must infer that no sibling handles images, but the negative guidance is unambiguous.

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