UNED Campus MCP Server

Overview Schema Source Related Servers Discussions Admin

uned_materiales

Lists downloaded course materials for a UNED subject, showing page counts and extracted text paths so students can locate and review readings.

Instructions

Lista los materiales descargados de una asignatura con nº de páginas y la ruta de su texto extraído.

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": {
      "asignatura": "<asignatura>"
    },
    "name": "uned_materiales"
  }
}

Input Schema

Name	Required	Description	Default
`asignatura`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 18, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the burden and does disclose that materials are 'descargados' (previously downloaded) and that results include page counts and an extracted-text path, implying a read-only listing. However, it does not state side effects, permissions, or whether it triggers downloads.

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 resource and the returned fields are stated efficiently.

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?

An output schema exists, so return values need not be explained, and the description still names the key fields. For a simple single-parameter query tool the definition is nearly sufficient, missing only parameter format and usage alternatives.

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?

Schema coverage is 0%, so the description must compensate. It does identify that the subject (asignatura) scopes the query, but gives no format guidance (course code vs. name, casing) for a string parameter that has no schema description.

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?

States a specific verb (listar) and resource (materiales descargados de una asignatura), plus hints at returned fields (nº de páginas, ruta del texto extraído). It does not differentiate itself from nearby siblings like uned_curso_contenido or uned_leer, but the purpose is unambiguous.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer it is used to enumerate materials for a given subject. There is no explicit when-to-use vs. when-not, and no mention of alternatives such as uned_curso_contenido or uned_leer for accessing content.

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