Skip to main content
Glama

trial_register_protocol

Register a hash-bound trial protocol; twins fork from the identical checkpoint, exactly one registered variable may differ.

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": {
      "protocol": "<protocol>",
      "checkpoint": "<checkpoint>",
      "treated_config": "<treated_config>"
    },
    "name": "trial_register_protocol"
  }
}

Input Schema

NameRequiredDescriptionDefault
protocolYes
checkpointYes
treated_configYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and discloses very little: it implies a mutation (registration) but says nothing about permissions/auth, whether registration is idempotent, whether a hash or ID is returned, or what happens if a second variable differs. "Hash-bound" hints at immutability but is never explained.

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 well-formed sentence with the core constraint front-loaded and no filler. It is efficient, though efficiency here partly reflects how little is said.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with three opaque nested-object parameters, no schema descriptions, no annotations, and no output schema, this is well short of what an agent needs to construct a valid call. Nothing explains the shape or required contents of protocol, checkpoint, or treated_config.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and all three parameters are unstructured nested objects, so the description must compensate and mostly does not. "checkpoint" is partially illuminated (twins fork from an identical checkpoint) and "exactly one registered variable may differ" loosely implies treated_config semantics, but "protocol" is left entirely unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

It names a specific verb and resource ("Register a ... trial protocol") and adds a domain rule about twins forking from an identical checkpoint with one differing variable. But the jargon is undefined and it never distinguishes this tool from the sibling lifecycle tools (trial_fork_pair, trial_run_pair), so the operation an agent should expect is only implied.

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?

No statement of when to call this versus trial_fork_pair or trial_run_pair, no ordering in the trial workflow, and no prerequisites (e.g., whether a protocol must be registered before forking). The single constraint sentence is a domain rule, not usage 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