Skip to main content
Glama

Diagnóstico del Sistema UCA

uca_diagnosticar_sistema
Read-onlyIdempotent

Audits connectivity, encrypted session status, graphical environment validity, and storage paths to verify that the UCA MCP environment is properly configured.

Instructions

Audita conectividad, estado de sesión cifrada, validez del entorno gráfico y rutas de almacenamiento.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.8
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedOutput schema / (root)
      Previous value: -{
      -  "$schema": "http://json-schema.org/draft-07/schema#",
      -  "additionalProperties": false,
      -  "properties": {
      -    "almacenamiento": {},
      -    "conectividad": {
      -      "additionalProperties": {
      -        "type": "string"
      -      },
      -      "type": "object"
      -    },
      -    "entorno": {},
      -    "servidor": {},
      -    "sesion": {}
      -  },
      -  "required": [
      -    "conectividad"
      -  ],
      -  "type": "object"
      -}New value: +null
  2. First observedv1.0.6

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description's value-add is naming the four probe areas (including network connectivity and disk paths), but it omits whether prior authentication is required, how long probing takes, and how partial failures are handled.

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 enumerating the audited areas with zero filler. Nothing is repeated from the annotations or schema, and every clause adds information.

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?

For a zero-arg read-only tool the description is close to sufficient, but there is no output schema, so the burden of explaining what the diagnostic returns (per-check pass/fail report? free-text log?) falls on the description and is left unaddressed. Prerequisites such as needing an active session are also unstated.

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 there is nothing for the description to disambiguate and no schema gap to compensate for. Baseline 4 applies; no parameter-level semantics are needed or missing.

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 ('audita') plus the exact facets inspected: connectivity, encrypted session state, graphical environment validity, and storage paths. That is far more informative than a tautology and distinguishes it from the data-retrieval siblings, though it never explicitly explains how it relates to session tools like uca_iniciar_sesion even though it touches 'estado de sesión'.

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?

There is no explicit when-to-use, when-not, or alternative named; the agent must infer that this is a pre-flight/troubleshooting check to run before or when other EVA/GUARANI calls fail. The diagnostic framing makes that inference reasonably safe, but the description does no work to route the agent.

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