Skip to main content
Glama

aula_get_site_info

Read-only

Fetches logged-in user and Moodle site details from the UTN virtual classroom, including the regional campus to tailor faculty-specific answers.

Instructions

Datos del usuario logueado y del sitio Moodle de su aula virtual. regional es la regional de la UTN de esa aula (por ejemplo, "Tucumán (FRT)"): usala para hablarle de su facultad.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful semantic context by explaining that regional identifies the UTN faculty (e.g. "Tucumán (FRT)"), but says nothing about what else the response contains or any auth assumptions.

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 short sentences with no filler; the resource identity is front-loaded and the field guidance follows. Slightly compressed Spanish phrasing but nothing wasted.

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?

With no output schema and no parameters, the description carries the burden of explaining what comes back. It names the user/site data and clarifies regional, but leaves the rest of the response shape unspecified.

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 still volunteers meaning for the regional value returned, which helps interpretation even though no parameters exist to document.

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 resource: data of the logged-in user plus the Moodle site of their virtual classroom. It is clear enough to distinguish from siblings like aula_list_courses or aula_read_file, though the verb is implicit and 'Datos ... del sitio' is somewhat broad.

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?

No explicit when-to-use or when-not-to-use guidance versus the eleven sibling tools. The one actionable hint is 'usala para hablarle de su facultad', which applies to interpreting the regional field rather than to selecting the tool.

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