Skip to main content
Glama

Plate map (6- to 384-well)

plate_map
Read-onlyIdempotent

Use when someone lays out a multiwell plate (ELISA, qPCR, cell or compound assays). Lays out a 6, 12, 24, 48, 96 or 384-well plate: standards, samples, controls and blanks with replicates, filled by row or column, optionally leaving edge wells empty and keeping replicate sets together. Returns a grid with a key and a well-by-well list.

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": "plate_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
blanksNoNumber of blank wells, placed last.
formatNo
samplesNoUnique sample names, in placement order.
controlsNoControl names (e.g. 'NTC', 'Positive control'), placed after samples.
plateNameNo
standardsNoOptional standard curve, placed first.
avoidEdgesNoLeave the outer wells empty to reduce edge effects.
replicatesNoReplicates per sample.
fillDirectionNoFill across rows (A1, A2, …) or down columns (A1, B1, …).row
controlReplicatesNoDefaults to the sample replicates.
keepReplicatesTogetherNoStart a new row or column instead of splitting a replicate set.

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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and side-effect behavior is covered. The description adds ordering semantics (standards first, samples, controls, blanks last), fill direction and edge-well behavior, which is genuine value beyond the annotations, but it omits details like limits on plate capacity overflow or what happens when content exceeds available wells.

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 usage trigger, then the layout semantics, then the return shape; there is no filler. The format enumeration (6 through 384) slightly duplicates the title and schema enum, which is minor redundancy rather than waste.

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 an 11-parameter, nullable-input tool with a nested standards object and an output schema, the description covers purpose, trigger context, layout rules and return shape. It does not need to explain return values since an output schema exists; only edge cases such as capacity overflow or conflicts between avoidEdges and content volume are unaddressed.

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 82%, so the schema already documents nearly all 11 parameters, including defaults and enum values. The description restates the field set and ordering in prose but contributes little syntax or constraint detail the schema does not already contain, making baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb ('lays out') and resource ('multiwell plate') and enumerates the supported formats and content types (standards, samples, controls, blanks). It is possible to distinguish the tool from siblings such as serial_dilution or solution_prep, though no sibling is explicitly contrasted.

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 when someone lays out a multiwell plate (ELISA, qPCR, cell or compound assays)' gives concrete trigger contexts. There are no explicit exclusions or named alternatives to route between, so it stops short of full when/when-not guidance.

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