Skip to main content
Glama

Course Access

course_access
Read-only

Retrieve admin-level course access details, including tags with student counts and teaching roles, to identify who accesses a course.

Instructions

(Admin) Quién accede a un curso: sus tags (con cantidad de alumnos) y los roles docentes.

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": {
      "course_id": "<course_id>"
    },
    "name": "course_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true, so safety is already covered. The description contributes contextual behavior beyond that: it is admin-restricted and it characterizes the payload (tags plus per-tag student counts, plus teaching roles). It does not say what happens for a nonexistent course or an unauthorized caller, nor anything about result size, which a read tool of this shape would benefit from.

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?

One short, front-loaded sentence with no filler, and the '(Admin)' constraint is placed first where it is most actionable. The parenthetical about student counts is compact and informative. Slight deduction only because the core verb is implicit rather than stated.

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?

The tool is simple (one parameter, read-only, output schema present so return shape need not be spelled out) and the description covers the admin gate and the data domain. It leaves unanswered what the agent should expect on empty results or access errors, which matters for an admin-scoped access-audit call. Adequate but thin for its complexity tier.

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 integer parameter, course_id, with 0% schema description coverage, so the description is the only place meaning could be added. It implies the course scope via 'de un curso' but adds nothing about identifier format, validity, or resolution. The parameter name is self-explanatory enough that the gap is small but real.

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 (who has access to a course) and enumerates the two components returned: the course's tags with student counts, and the teaching roles. An agent can tell this apart from sibling read tools like course_topics or course_results. It only stops short of a strong verb, since 'quién accede' describes the subject rather than the retrieval action.

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?

The only usage signal is the '(Admin)' prefix, which conveys a permission prerequisite rather than when to pick this over an alternative. There is no explicit when-to-use, no exclusion, and no mention of related siblings such as course_topics or list_tags that could cover adjacent data. The agent must infer the call context from the name alone.

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