Campus Virtual MCP

list_courses

Read-onlyIdempotent

Retrieves visible Grado courses from My courses and returns each course ID, full name, and URL to help identify and access enrolled subjects.

Instructions

Lista las materias visibles en My courses → Grado, con ID, nombre completo y URL.

Sin parámetros. Autentica con la configuración privada de .env y comparte la sesión de Lightpanda con las demás herramientas. Incluye Sistemas y Básicas y todos los años presentes en esa rama; excluye Ingreso, Extensión y el catálogo general. Devuelve scope=Grado, source_url, fetched_at, total, courses y complete=true. Una rama pendiente, un límite o un fallo de sesión/parsing producen un error MCP, nunca una lista vacía exitosa. No abre cada materia ni modifica datos académicos. Los nombres parecidos se devuelven como materias distintas con sus respectivos IDs.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Default
`scope`	No	Grado
`total`	Yes
`courses`	Yes
`complete`	No
`fetched_at`	Yes
`source_url`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 2, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Adds substantial context beyond the annotations: it discloses the shared Lightpanda session model with other tools, the exact response envelope (scope, source_url, fetched_at, total, courses, complete=true), and a strong failure semantic — a pending branch, limit or session/parsing failure yields an MCP error, never a successful empty list. The 'never mutates academic data' statement is consistent with readOnlyHint=true and destructiveHint=false.

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?

Front-loaded with purpose and scope, then return shape, then failure semantics, then boundaries — a sensible order with little waste. It is on the dense side (several clauses per sentence) and the enumerated return keys partially duplicate the output schema.

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 parameterless, read-only listing tool the description covers scope, exclusions, auth/session behavior, error semantics, non-mutation and duplicate-name handling. Even though an output schema exists, the explicit failure-mode note ('never a successful empty list') adds information the schema cannot convey.

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?

Zero parameters, so the baseline is 4; the description confirms 'Sin parámetros' rather than leaving the agent to infer it. Nothing further is required on this dimension.

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?

Opens with a specific verb+resource+scope: 'Lista las materias visibles en My courses → Grado, con ID, nombre completo y URL'. It also delimits the resource boundary (includes Sistemas/Básicas and all years, excludes Ingreso, Extensión and the general catalogue), which lets an agent distinguish it from get_course_resources without opening either 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 states 'Sin parámetros' and enumerates what is excluded (Ingreso, Extensión, catálogo general) plus 'No abre cada materia', which implicitly routes deeper lookups to a sibling. It stops short of naming the alternative tool (e.g. get_course_resources) or stating prerequisites for the session beyond 'Autentica con la configuración privada de .env'.

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

Deploy Server