Skip to main content
Glama

quien_soy

Shows the connected Moodle user and site so you can verify that your mobile-app token is valid and working before accessing courses, deadlines, or grades.

Instructions

Muestra el usuario y el sitio Moodle conectados (sirve para comprobar el token).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the disclosure burden. It implicitly frames the tool as a safe read/diagnostic ('conectados', 'comprobar el token'), which is helpful, but it says nothing about what happens with an invalid or expired token, or whether any session state changes.

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 short sentence with the returned data front-loaded and the diagnostic use case in a parenthetical. Nothing is padded or redundant.

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 zero-parameter, no-output-schema tool, the description does the necessary work by naming what is returned (user and site), which substitutes for the missing return-value documentation. Only the failure/invalid-token behavior is left 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 no parameter-level meaning to add; baseline applies. The description correctly implies no input is needed.

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 ('Muestra') and a specific resource pair ('el usuario y el sitio Moodle conectados'), so an agent knows exactly what it returns. It is easily distinguished from the content-oriented siblings (cursos, tareas, mensajes) even though it does not name them.

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

Usage Guidelines4/5

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

The parenthetical '(sirve para comprobar el token)' gives a concrete when-to-use condition: verifying that credentials/token are valid. It stops short of explicit when-not guidance, but no sibling appears to overlap with this diagnostic role, so the gap is minor.

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