Skip to main content
Glama

Find a clinical research career path

career_path
Read-onlyIdempotent

For a clinical research role and a country, link to CRLN's Career Path Finder page for that role and country, plus free training for it.

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

Input Schema

NameRequiredDescriptionDefault
roleNoThe role, for example CRC, CRA, research nurse or regulatory.
countryNoThe country, for example Nigeria or United States.
languageNoPreferred language. Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish readOnly, closed-world, idempotent behavior, so the description's real contribution is disclosing the return shape: a link to an external page rather than the career content itself, plus a training pointer. That is exactly the kind of context an agent needs since there is no output schema. It stops short of saying what happens when a role or country is unrecognized.

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 front-loaded sentence with no filler, though 'for that role and country' is slightly redundant after the opening clause. Nothing needs to be cut, but a clause on missing inputs would earn its place more than the repetition.

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

Completeness3/5

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

For a simple lookup the description covers inputs, output nature and safety is handled by annotations. The notable gap is that all three parameters are optional, and the description never says what the tool does when role, country or language is omitted. Without an output schema it also leaves the language parameter's effect unstated.

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% and each parameter carries its own description with examples (CRC, CRA, Nigeria, United States), so the schema does the heavy lifting. The description only restates the role/country pairing and adds no format, casing or fallback guidance beyond it. Baseline 3 applies.

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 pairs a specific resource (CRLN's Career Path Finder page) with the two inputs that select it, and says it also surfaces free training. That distinguishes it clearly from siblings like check_answer, explain_rule and practice_decision, though it never names them 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 can infer this is for career-path questions in clinical research, and the role/country framing hints at the trigger. There is no explicit when-to-use or when-not statement, and no mention of how it differs from the other learning-oriented siblings.

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