Skip to main content
Glama

Electronic lab notebook entry template

eln_template
Read-onlyIdempotent

Build an electronic lab notebook (ELN) entry template for an experiment: objective, materials, procedure, observations and conclusion sections from a preset or custom list, optionally with timestamp fields and voice-capture prompts. Returns Markdown and HTML.

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

Input Schema

NameRequiredDescriptionDefault
presetNoAlias for presetId.
presetIdNoELN template preset to use.
sectionsNoAlias for sectionItems.
sectionItemsNo
experimentTitleNoTitle for the ELN entry template.
includeTimestampsNoWhether to include record metadata fields.
includeVoicePromptsNoWhether to include Verbex-style section voice prompts.

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.5/5.0
Behavior3/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 the safety profile is covered. The description adds useful context by naming the return formats (Markdown and HTML) and the optional timestamp and voice-prompt features, but says nothing about preset-vs-custom precedence or how library section ids are resolved.

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?

A single dense sentence that front-loads the action and resource, then lists sections and return formats. Every clause carries information; only the parenthetical expansion of ELN is mildly redundant with the title.

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 annotations cover the safety profile. It is complete enough for a zero-required-parameter builder, with only the alias/precedence behavior between preset and presetId left unstated.

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 documents preset, presetId, sections, sectionItems, experimentTitle and the two booleans. The description restates the preset-or-custom choice and the optional timestamp/voice fields but adds no syntax or precedence detail beyond the schema, so baseline 3 applies.

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 an electronic lab notebook (ELN) entry template for an experiment') and enumerates the sections produced, plus the return formats. It does not explicitly differentiate itself from the sibling protocol_template, so it falls short of a 5.

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?

Usage is only implied by the phrase 'for an experiment'; there is no explicit when-to-use, when-not-to-use, or named alternative such as protocol_template. An agent can infer the context but gets no routing 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