Skip to main content
Glama
Sign In
utn-mcp

utn-mcp

by nialvape
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

aula_list_courses

Read-only

Lists the courses a user is enrolled in within the UTN virtual classroom, returning each course's address for opening it.

Instructions

Lista los cursos (materias) en los que está inscripto el usuario. Es el punto de entrada: cada curso viene con su direccion, que se le pasa a aula_open para entrar.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds valuable output context absent from any output schema: each course includes a `direccion` field intended for aula_open. It doesn't mention auth/session requirements or ordering, but adds real behavioral value beyond annotations.

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?

Two short sentences, zero waste: the first states what is listed, the second delivers the workflow-critical detail (the `direccion` handoff) immediately. Front-loaded and easy to scan.

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

Completeness5/5

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

For a zero-parameter entry-point tool with no output schema, the description covers purpose, user scoping, the returned field that matters, and the next call. Safety is already covered by annotations, so nothing an agent needs to invoke it correctly is missing.

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 tool takes zero parameters, so the baseline is 4. The description correctly implies no input filtering is needed and instead explains the shape of each returned item, which is the relevant semantic detail here.

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

Purpose5/5

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

States a specific verb and resource ('Lista los cursos... en los que está inscripto el usuario') and immediately positions itself in the workflow as 'el punto de entrada', distinguishing it from aula_open by naming the handoff via `direccion`. An agent can identify its role without reading any schema.

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

Usage Guidelines4/5

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

Explicitly frames the tool as the entry point and names the follow-up action (pass `direccion` to aula_open), which tells the agent when to call it first. It does not state exclusions or what to do if the list is empty, but the sequencing guidance is clear.

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

Deploy Server

Other Tools