Skip to main content
Glama

trial_fork_pair

Fork a checkpoint-paired assignment for one task (blinded arms A/B).

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": {
      "trial_id": "<trial_id>",
      "task": "<task>"
    },
    "name": "trial_fork_pair"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYes
trial_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2/5.0
Behavior1/5

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

No annotations are provided and the description does not disclose side effects, prerequisites, idempotency, authorization needs, or what 'blinded arms A/B' implies operationally. It gives no behavioral information beyond the name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no wasted words, but its brevity leaves key terms undefined rather than front-loading useful context. It is concise but under-specified for a two-parameter workflow action.

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?

There is no output schema and no annotations, and the input schema has a nested object with unspecified fields. The description does not fill these gaps, leaving an agent without enough context to invoke the tool correctly.

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 both parameters are required. The description vaguely implies 'task' but does not explain trial_id, the nested task object's expected fields, or the relationship between the two parameters.

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?

The sentence names a specific verb ('Fork') and resource ('checkpoint-paired assignment for one task'), but the meaning of 'checkpoint-paired' and 'fork' in this workflow is not clear enough to distinguish it confidently from trial_run_pair or trial_register_protocol.

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

Usage Guidelines1/5

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

There is no indication of when to use this tool, when not to use it, or which sibling tool it replaces or complements. An agent must infer the entire workflow context from the name alone.

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