Skip to main content
Glama

Explain a GCP rule

explain_rule
Read-onlyIdempotent

Plain-language answer from CRLN's published pages to a question about ICH E6(R3), Good Clinical Practice, US FDA rules for site staff, free GCP training, clinical research careers, or taking part in research, with the primary sources cited and a link straight to the page. Says so when CRLN has no page for the question.

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": {
      "question": "<question>"
    },
    "name": "explain_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionYesThe question, in the person's words.

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 establish read-only, idempotent, and closed-world (openWorldHint=false). The description adds real behavior beyond that: answers cite primary sources, include a direct link to the page, and explicitly disclose when CRLN has no page for the question, which is a meaningful honesty/fallback trait an agent needs to interpret the result.

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?

It is one long sentence, but the core outcome (plain-language answer with citations and link) is front-loaded and the no-coverage behavior follows. The topic enumeration is somewhat list-heavy but each item bounds the corpus, so little is wasted.

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 carries the burden of explaining returns, and it does: plain-language answer, cited primary sources, and a page link, plus the negative case where no CRLN page exists. Only the overlap with the careers/decision siblings is left unresolved.

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?

There is a single required parameter with 100% schema coverage, so the baseline is 3. The description's topic enumeration adds modest scoping value by signalling the kinds of questions the corpus covers, but it adds no format or phrasing requirements beyond what the schema already states.

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 names a concrete verb and resource: a plain-language answer drawn from CRLN's published pages, with an explicit topic scope (ICH E6(R3), GCP, FDA rules for site staff, training, careers, participation). It is clear what the tool returns, though it does not name a sibling (e.g. career_path) to sharpen the boundary where the careers topic overlaps.

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 implied by the topic list — ask a question about a GCP rule or related CRLN subject — but there is no explicit when-to-use/when-not guidance and no routing toward check_answer, practice_decision, or site_readiness_info. An agent can infer the context but must decide on its own between this and the decision/practice tools.

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