Skip to main content
Glama

read_eds_run

Read-only

Read an Applied Biosystems / Thermo QuantStudio .eds experiment: what the run holds (its name, plate, dyes, collection points and stages) and, on request, the amplification curves as a cycle × well table ready for call_cq. read_rdml_run reads the other instrument format; an .eds is not an RDML document in another spelling, so it has its own reader.

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

Input Schema

NameRequiredDescriptionDefault
dyeNothe reporter dye the curves are read from. Empty takes the run's first dye, and the answer says which. Only applies when curves is true.
fileNothe `.eds` to read, by name, from the project or the `_files` sent with the call. Empty reads the only one there.
_filesNoThe project: record references shaped like _subject. Their records become library documents a tool names in sequences/parts/document; a trace or alignment is found by file name.
curvesNoalso return the amplification curves as a cycle × well table (tab-separated), which is what call_cq takes as its `table`.
_subjectNoThe record to act on: exactly one of sequence, accession (+source), sample (an id from list_samples) or file ({name, text} or {name, base64}); record_index picks one record of several.
passive_referenceNothe dye to normalise against, giving Rn (reporter ÷ passive). Empty emits the raw reporter signal and says so: picking ROX silently would be a normalisation nobody chose. Only applies when curves is true.

Output Schema

NameRequiredDescriptionDefault
dyesYesthe dyes this run carries, in the archive’s order
tableYesthe amplification curves as a tab-separated cycle × well table, when `curves` was asked for. Wire it into call_cq
wellsYeswells the archive holds readings for
pointsYescollection points — the cycles, which is what a curve has to be fitted over
summaryYesthe run as the archive states it: name, specVersion, plate, wells, collection points, dyes and the stages they came from
normalizationYeswhat the table carries: the reporter's raw signal, or Rn against the named passive reference

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false, and closed-world scope, so safety is covered. The description adds real behavioral detail beyond that: curves come back as a tab-separated cycle × well table shaped for call_cq, and the defaults for dye and passive_reference are surfaced rather than silently chosen, which matters for interpreting Rn versus raw reporter signal.

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 what the tool returns and followed by the routing rule. The clause about `.eds` not being an RDML document in another spelling is slightly conversational but earns its place by preventing a common misroute.

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 description need not explain return values, and it correctly focuses on content and the curve-mode contract. It covers the main decision points for a six-parameter read tool, though it says nothing about failure modes (missing or ambiguous `.eds`) beyond what the schema implies.

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% and the schema already spells out dye defaulting, passive_reference normalisation, and the curves table format, so the description mostly restates that. The only marginal addition is the explicit downstream contract that the curve table is what call_cq consumes, which is also echoed in the schema. Baseline 3 applies when the schema carries the parameter semantics.

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 gives a specific verb plus resource (read an Applied Biosystems / Thermo QuantStudio `.eds` experiment) and enumerates the payload: run name, plate, dyes, collection points, stages, and optional amplification curves. It explicitly separates itself from read_rdml_run by stating the `.eds` is a distinct format with its own reader, so an agent can route without inspecting either schema.

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?

It names the sibling alternative read_rdml_run and states the condition that selects it (other instrument format), and it points forward to call_cq when curves are wanted. It stops short of explicit exclusions or prerequisites, such as requiring the file to be present in the project or what to do when several `.eds` files exist.

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