Skip to main content
Glama

Lab protocol template

protocol_template
Read-onlyIdempotent

Build a structured lab protocol (purpose, materials, procedure, critical steps, acceptance criteria and more) for a protocol title, using a preset or custom sections. Returns Markdown and HTML ready to fill in or print.

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

Input Schema

NameRequiredDescriptionDefault
presetNoAlias for presetId.
presetIdNoProtocol scaffold preset to use.
sectionsNoAlias for sectionItems.
sectionItemsNo
protocolTitleNoTitle for the protocol scaffold.
includeExecutionNotesNoWhether to include ELN execution notes for running the protocol.
includeVersionHistoryNoWhether to include protocol version history when present in sectionItems.

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.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing the return artifacts ('Markdown and HTML ready to fill in or print'), clarifying that 'Build' produces a document rather than persisting anything. It stops short of noting default behavior when no preset or sections are supplied.

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 action and content list front-loaded and the return format last. Every clause contributes information an agent needs.

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?

An output schema exists, so the description need not explain return values, and its mention of Markdown/HTML is a useful pointer rather than a burden. For a 7-parameter builder with all-optional inputs, the description could say what happens when no preset or sections are given, but it is otherwise complete.

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 86%, so the schema already carries parameter meaning, and the baseline of 3 applies. The description only alludes to 'a protocol title' and 'preset or custom sections' without explaining the preset/library/custom section interaction or the alias pairs (preset/presetId, sections/sectionItems).

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?

States a specific verb and resource ('Build a structured lab protocol') and enumerates the produced parts (purpose, materials, procedure, critical steps, acceptance criteria), which makes the tool's output concrete. It does not distinguish itself from the sibling 'eln_template', which an agent could easily confuse with this template builder.

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

Usage Guidelines3/5

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

Implies usage through 'for a protocol title, using a preset or custom sections', giving the agent a sense of the two construction modes. However, there is no explicit when-to-use/when-not guidance and no named alternative (e.g., eln_template) to route between, leaving selection to inference.

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