Skip to main content
Glama

Course Results

course_results
Read-only

Fetch aggregated assessment outcomes for a specific course ID to monitor performance.

Instructions

Resultados agregados de un curso (monitor).

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_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
course_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

The readOnlyHint=true annotation already establishes that this is a safe read, and the description is consistent with it. Beyond that, "agregados" implies pre-computed summaries rather than per-student rows, but the description says nothing about aggregation level, authorization requirements implied by "monitor", or whether the course must exist, so it adds only marginal behavioral value.

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

Conciseness3/5

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

A single short sentence with no filler, and the key information is front-loaded. But the brevity is achieved through under-specification rather than tight editing, since the parenthetical "(monitor)" uses space without conveying meaning.

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

Completeness2/5

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

An output schema exists, so return values need not be described, and there is only one required parameter. Even so, for a results-reporting tool that competes with two sibling result tools, the description omits what makes the data "aggregated" and what "monitor" implies, which is the information an agent would actually need to choose it correctly.

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

Parameters2/5

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

Schema description coverage is 0%, so the single parameter course_id is documented nowhere. The description does not say what a course identifier is, how to obtain one, or whether it must reference a course the caller monitors, leaving the parameter entirely to inference from its name.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource (course results) and adds that the values are aggregated, which is more than a restatement of the name. However, the trailing qualifier "(monitor)" is opaque and it does not distinguish this tool from the sibling results tools student_results and test_results, so the agent cannot tell which result grain to pick from the purpose alone.

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 guidance on when to use this tool instead of student_results or test_results, and no stated prerequisites such as needing monitor-level access. The only contextual cue is the word "monitor" in parentheses, which is never explained.

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