Skip to main content
Glama

Future Micro Mold Lab

How to run a study

get_study_protocol
Read-onlyIdempotent

Return the full procedure for one study: what it is for, the equipment needed, the step-by-step method at the press, and what a good result looks like, so the numbers collected at the press are the ones the calculation needs.

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

Input Schema

NameRequiredDescriptionDefault
studyYesWhich study to explain

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?

Annotations already declare readOnlyHint, idempotentHint, closed-world and non-destructive, so the safety profile is covered. The description adds genuine behavioral context: the call returns instructional content (equipment list, press-side method, acceptance criteria) rather than measurements, and it states the intent behind the content. It does not say how long the returned procedure is or how it is formatted.

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?

One sentence, front-loaded with the action and resource, then the returned sections. The trailing rationale ('so the numbers collected at the press are the ones the calculation needs') earns its place by explaining why the procedure matters, though the sentence is dense enough that a bulleted structure would scan better.

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 no output schema, the description must convey return content, and it does so by listing the four sections an agent will receive. For a simple single-parameter read tool with full safety annotations, the only gap is the return format and nothing about invalid or ambiguous study values.

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 coverage is 100% with a single enum parameter already described as 'Which study to explain,' so the schema carries the load. The description reinforces that exactly one study is in scope and that the returned procedure is specific to it, but adds no detail about the eight enum values or their differences.

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?

Specific verb ('Return') plus resource ('the full procedure for one study') followed by an enumeration of the four content sections: purpose, equipment, step-by-step method, and result criteria. This clearly separates it from siblings like viscosity_curve or cavity_balance, which appear to be the execution tools, though the description never states that distinction explicitly.

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: an agent infers 'call this when you need to know how to run a study.' There is no statement of when not to use it and no reference to the sibling study tools that likely execute the procedure, which is the most likely confusion point.

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