Skip to main content
Glama

What the CRLN Site Portal does for research sites

site_readiness_info
Read-onlyIdempotent

What CRLN's free Site Portal does for clinical research sites (training records, staff readiness, a readiness record for sponsors), with a link. It cannot see or change any site's data.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds genuine scope information beyond them: it states the tool cannot see or change any site's data, which tells the agent this is a bounded marketing-style overview rather than a data-access tool.

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 with the subject and the content list front-loaded, followed immediately by the data-access disclaimer. The parenthetical inventory is compact and every clause carries information; wording is slightly circular ('What CRLN's free Site Portal does for research sites' restating the title).

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?

For a zero-parameter, read-only informational tool with no output schema, the description supplies enough: what topics it covers, that it includes a link, and that it touches no site data. Only the boundary against sibling tools is left unstated.

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

Parameters4/5

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

There are zero parameters, so the schema imposes no documentation burden and the baseline is 4. The description correctly treats this as a no-argument informational call and does not invent input semantics.

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 specific resource — CRLN's free Site Portal — and enumerates its parts (training records, staff readiness, a readiness record for sponsors), so an agent knows what content the tool surfaces. It is clear about being informational, though the framing is more 'what this thing is' than a crisp verb-led statement of what the tool returns.

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 the tool for questions about the Site Portal's purpose and features. There is no explicit when-to-use, when-not-to-use, or pointer to a sibling tool for adjacent questions such as career paths or rules.

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