Skip to main content
Glama
Moodle MCP Server
by d1zcipline

moodle_whoami

Retrieves the signed-in user's name and ID plus site name, release, and available API function count, confirming identity and connection when an agent needs context.

Instructions

Signed-in user: full name, user id, site name/release and the number of API functions available.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It does useful work by disclosing the return payload (identity fields plus site release and function count), which lets an agent anticipate what comes back. It says nothing about authentication requirements, failure behavior when not signed in, or whether the call is side-effect free, leaving real gaps.

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 that front-loads the subject ('Signed-in user') and then lists exactly the returned fields. No filler, no redundancy, and every clause carries 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 trivial zero-parameter identity probe with no output schema, the description is nearly sufficient — it enumerates the returned fields in the absence of a structured return definition. The only shortfall is the lack of any note about auth state or what happens when no session exists.

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 beyond the schema; baseline 4 applies. The description does not need to explain argument meaning and correctly omits any.

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?

The fragment 'Signed-in user' plus the enumerated fields (full name, user id, site name/release, API function count) makes it unambiguous that this returns the current identity/session context. It is clearly distinct from the sibling tools, which all deal with courses, files, and assignments. It loses a point only because there is no explicit verb — the reader must infer 'returns/reports'.

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?

Usage is only implied: naming the resource 'Signed-in user' suggests calling it to establish identity or verify a session, but there is no explicit when-to-use statement, no mention of a prerequisite (e.g. a valid token), and no reference to alternatives. For a zero-parameter introspection tool the implied usage is fairly strong, so a 3 rather than a 2.

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