Skip to main content
Glama
TrialRun MCP

TrialRun MCP

by kostadindev

Get access policy

get_access_policy

Show the student's access checklist to reveal which files the AI may and may not open.

Instructions

Show the student's access checklist: which files the AI may and may not open.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does convey useful behavior — that the result is a per-student checklist of allowed versus forbidden files — but never states that the call is read-only, what permissions or session context are needed, or whether the policy is scoped to the current student.

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

Conciseness5/5

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

A single front-loaded sentence with no filler. The clarifying colon phrase earns its place by defining what "access checklist" means.

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 and no annotations, the description usefully characterizes the return value (may/may-not-open file lists) and requires no inputs. It is nearly complete for a trivial zero-parameter getter, with only the read-only/permission framing left unsaid.

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?

The input schema has zero parameters, which is the baseline-4 case; there is no parameter meaning to add. The description does not introduce spurious arguments or ambiguity about how to invoke it.

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 gives a specific verb and resource ("Show the student's access checklist") and even clarifies the content — which files the AI may and may not open. That makes it distinguishable from read-oriented siblings like get_audit_log or get_report, though it never names an alternative to contrast with.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, no prerequisites, and no mention of alternatives such as get_audit_log for historical access data. The purpose hints the tool answers permission questions, but the agent must infer that entirely.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.