Skip to main content
Glama

Future Micro Mold Lab

Open a study data sheet

open_study_sheet
Read-onlyIdempotent

Open an empty data sheet for one study in an interactive card: the procedure beside a table the person fills in or pastes into, with the result computed as they type. Also returns the procedure as text and a link to the same calculator on the Lab website.

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": {
      "study": "<study>"
    },
    "name": "open_study_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
studyYesWhich study
setpointsNoSetpoints fixed so far, shown above the sheet

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and a closed-world scope. Beyond those annotations, the description adds that the tool returns an interactive card, procedure text, and a web link, and that results update as the user types. It does not say what the returned card object looks like or what happens with an invalid study value, which leaves only minor gaps.

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 action is stated first, and details follow in one dense but well-ordered sentence. The middle clause uses the phrase "the procedure beside a table the person fills in or pastes into," which is slightly involved but still readable. Nothing is padded.

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?

Without an output schema, the description carries the job of explaining what comes back, and it does: a card, procedure text, and a link. For a tool with 2 parameters, full schema coverage, and rich annotations, the definition covers what an agent needs to call it. Minor gaps are the lack of any note on failure modes or validation of the study enum.

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 documents both `study` and `setpoints`. The description adds only the word "empty": the sheet starts empty, and the setpoints supplied are shown above it rather than pre-filled. That is useful framing but no detail on the study choices.

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 names a specific action and resource: "Open an empty data sheet for one study in an interactive card." It also states the concrete deliverable: procedure, an editable table, and live-computed results. It does not name a sibling as an alternative, even though overlapping siblings such as get_study_protocol and the per-study calculators exist.

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?

The text implies when to use the tool: when the user wants to fill in or paste data and have results computed live. The phrase "a link to the same calculator on the Lab website" hints that a web equivalent exists, but the description never says when to pick this tool over get_study_protocol or the individual study tools. The agent has to infer that choice.

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