Skip to main content
Glama

analyze_rt_pcr

Read-only

What a primer pair does on a SPLICED transcript versus genomic DNA: the products on each, whether a primer straddles an exon junction (so the assay cannot amplify gDNA at all), whether genomic DNA would still give a band, and by how many bases the two products differ on a gel.

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": {
      "forward": "<forward>",
      "reverse": "<reverse>"
    },
    "name": "analyze_rt_pcr"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNomin 3' footprint match length (pydna `limit`). In bp. Advanced.
_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.
forwardYesforward primer 5'→ 3'.
reverseYesreverse primer 5'→ 3'.
_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.
end_lengthNo3'-most bases that must pair exactly whatever the mismatch budget. Advanced.
mismatchesNosubstitutions a primer may carry and still prime (QUEEN `{s<=N}`). 0 is pydna's exact search. Advanced.
transcriptNothe joined mRNA or CDS annotation to splice, by NAME. Left empty the record's only joined annotation is used, and several are refused with their names.

Output Schema

NameRequiredDescriptionDefault
intronBpYesintron removed by splicing — the size difference between a genomic and a transcript product on the gel
productsYesone row per product: its transcript interval, its genomic interval, the genomic PIECES a spliced product maps to (several when it spans a junction), and whether it forms on the transcript only, genomic only, or both
placementsYesper primer: where it binds on the transcript, and which junction offsets its footprint straddles
gdnaWouldAmplifyYesthe same pair also makes a product on genomic DNA, so a contaminated RNA prep gives a band
junctionSpanningYesa primer's own footprint straddles an exon junction, so this pair cannot prime on genomic DNA at all — the property an RT-PCR assay is designed for. Branch a workflow on this
transcriptLengthBpYeslength of the spliced transcript

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

The read-only annotations already establish the safety profile, and the description adds useful behavioral detail about what the analysis reports: products on each template, exon-junction straddling, gDNA band presence, and gel size difference. It does not add operational caveats such as assumptions or limitations, so it is adequate but not rich.

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?

The description is a single front-loaded sentence that packs the key comparison and outcomes without wasted preamble. The embedded list makes it slightly dense, but it is appropriately sized for the tool.

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 a complex tool with an output schema and fully documented parameters, the description provides enough conceptual context to understand the analysis being performed. It is somewhat thin on invocation guidance, but the schema and annotations carry the structured details.

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 the schema already defines parameters such as limit, end_length, mismatches, and transcript by name. The description adds only high-level meaning by framing the call as a primer-pair versus spliced/gDNA comparison, without explaining parameter usage beyond the schema.

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?

The description gives a specific analysis: comparing what a primer pair produces on a spliced transcript versus genomic DNA and checking exon-junction straddling. This is clearly distinct from generic PCR amplification work, though it does not explicitly name sibling alternatives such as pcr_amplify or multiplex_pcr.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the use case of RT-PCR primer specificity analysis, but it gives no explicit when-to-use guidance, no exclusions, and no routing to alternatives. An agent must infer that this is for checking whether a primer pair is transcript-specific versus gDNA-amplifying.

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