Skip to main content
Glama

Practice a clinical research decision

practice_decision
Read-onlyIdempotent

Get one real clinical research decision from CRLN's public Practice Lab scenarios: the situation, the question and the options, with no answer. Optional role filter (for example CRC, CRA, CTA, PI, regulatory, data manager, research nurse, pharmacovigilance). Show the options to the person and let them choose before calling check_answer.

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

Input Schema

NameRequiredDescriptionDefault
roleNoRole to practice, for example CRC, CRA, PI or regulatory. Optional.
languageNoPreferred language, for example es or Spanish. Decisions are served in English for now; the CRLN page offers other languages.
scenario_idNoA specific public scenario id, to show that decision again. Optional.

Output Schema

NameRequiredDescriptionDefault
linkNoA link straight to the page on CRLN.
roleNo
titleNo
optionsNo
settingNo
languageNo
questionNo
role_nameNo
situationNo
attempt_idNo
scenario_idNo
decisions_in_scenarioNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds an important trait not in annotations: the payload deliberately omits the answer, and the agent is expected to surface options to a human – behavior an agent would otherwise get wrong.

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?

Two sentences, front-loaded with the core action and the deliberately-missing answer, followed by the usage instruction. The parenthetical role list is slightly long but serves as useful disambiguation rather than filler.

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?

An output schema exists, so return structure need not be explained. The description covers the key behavioral trap (no answer returned) and the follow-up tool, leaving little an agent needs to call this correctly.

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 baseline is 3. The description repeats the optional role filter with a slightly broader example list (data manager, research nurse, pharmacovigilance) but adds no syntax or semantics beyond what the schema provides for role, language, or scenario_id.

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

Purpose5/5

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

The description gives a specific verb and resource: fetch one real clinical research decision (situation, question, options) from CRLN's Practice Lab. It explicitly states what is included and what is not ('with no answer'), which separates it cleanly from the sibling check_answer.

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

Usage Guidelines4/5

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

It names the workflow condition: present the options to the person, let them choose, then call check_answer. That is clear when-to-use guidance tied to a named sibling. It does not address when to prefer career_path or site_readiness_info, so it falls short of full exclusion 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