UNED Campus MCP Server

Overview Schema Source Related Servers Discussions Admin

uned_progreso_marcar

Update a UNED subject topic's progress status—pending, reading, seen, reviewed, or mastered—and add optional notes for doubts or test scores.

Instructions

Actualiza el estado de un tema: pendiente, leyendo, visto, repasado o dominado. tema: nombre o número (p. ej. '3' o 'Tema 3'). nota: comentario opcional (dudas, puntuación de test…).

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>",
      "tema": "<tema>",
      "estado": "<estado>"
    },
    "name": "uned_progreso_marcar"
  }
}

Input Schema

Name	Required	Description	Default
`nota`	No
`tema`	Yes
`estado`	Yes
`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

B3.2/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the allowed estado values (pendiente, leyendo, visto, repasado, dominado), which the schema lacks, but it says nothing about permissions, whether the update is reversible, or what happens to a previously set state. Genuine but partial behavioral disclosure.

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?

Two tight sentences: purpose first, then per-parameter hints. No filler. Slightly terse rather than padded, which is the right trade-off here.

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?

An output schema exists, so return values need not be described, and the estado enumeration is helpful. However, the missing semantics for asignatura and the absence of any usage/routing guidance leave real gaps for a 4-parameter mutation tool with no annotations.

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 explains tema (name or number, with an example) and nota (optional comment, with examples), and lists estado's possible values, but the required asignatura parameter is left entirely unexplained. Partial compensation only.

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?

Estates a specific verb (Actualiza) plus resource (estado de un tema) and enumerates the valid states, so an agent immediately understands the operation. It is distinguishable from the sibling uned_progreso (which reads progress), though it does not name that sibling explicitly.

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 description says what the tool does but offers no when-to-use / when-not-to-use guidance and does not name alternatives such as uned_progreso. Usage is only implied by the verb, and no prerequisites (e.g. login) are mentioned.

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