Skip to main content
Glama
Sign In
UCA MCP

UCA MCP

by santinohicke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

[EXPERIMENTAL] Aranceles y Trámites en Campus

campus_aranceles_y_tramites
Read-onlyIdempotent

Retrieves current and pending fees plus administrative procedure status from Campus Autogestión, including balance, eligibility to study or take exams, and active procedures.

Instructions

[EXPERIMENTAL] Consulta aranceles al día/pendientes y estado de trámites administrativos en Campus Autogestión. Incluye saldo, habilitación para cursar/rendir y trámites en curso.

Input Schema

NameRequiredDescriptionDefault
consultaNoFiltro de consulta: 'todo', 'aranceles' o 'tramites' (por defecto: todo)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.0
    • removedInput schema / properties / consulta / default
      Removed value: -"todo"
    • changedInput schema / properties / consulta / description
      Previous value: -"Filtro de consulta: 'todo', 'aranceles' o 'tramites'"New value: +"Filtro de consulta: 'todo', 'aranceles' o 'tramites' (por defecto: todo)"
  2. Changed3 schema fields changedv1.0.8
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "aranceles": {
-      "type": "array"
-    },
-    "errores": {
-      "additionalProperties": {
-        "type": "string"
-      },
-      "type": "object"
-    },
-    "estadoAranceles": {
-      "type": "string"
-    },
-    "tramites": {
-      "type": "array"
-    }
-  },
-  "type": "object"
-}New value: +null
  3. First observedv1.0.6

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds scope context — that it returns balance, eligibility to sit exams, and in-progress paperwork — but says nothing about session/auth prerequisites (there is a uca_iniciar_sesion sibling) or about freshness of the data, which matters for a "al día/pendientes" query.

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 that front-load the resource and then list returned data. Minor waste: the "[EXPERIMENTAL]" marker is duplicated verbatim from the title, costing space without new information.

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?

For a one-optional-param, read-only tool with no output schema, the description covers what the agent needs to decide to call it and what categories of data come back. It stops short of indicating result shape or whether a session must already exist, which is the only meaningful gap.

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?

There is a single optional enum parameter with 100% schema description coverage, so the schema already explains 'todo'/'aranceles'/'tramites' and the default. The description never references the filter, adding no meaning beyond the enum. Baseline 3 applies.

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 ("Consulta") and two concrete resources (aranceles, trámites administrativos), then enumerates the data returned: saldo, habilitación para cursar/rendir, trámites en curso. That is enough to tell it apart from the eva_* and guarani_* siblings, but it never names an overlapping sibling (e.g. guarani_estado_cursada) to disambiguate the academic-status overlap.

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?

The domain (Campus Autogestión fees and administrative paperwork) implies when to reach for it, but there is no explicit when-to-use, when-not-to-use, or named alternative among the 20 sibling tools. An agent must infer that this is the place for payment status versus guarani_mis_inscripciones_examen for exam registration.

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