Skip to main content
Glama
Sign In
ufsc-moodle-mcp

ufsc-moodle-mcp

by jeanmartina
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Informações da conta e do Moodle

get_site_info
Read-onlyIdempotent

Retrieves the authenticated user's ID, full name, and username along with UFSC Moodle site information to verify session identity and instance details.

Instructions

Retorna informações do usuário autenticado (userid, nome completo, username) e da instância do Moodle da UFSC.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that the data is scoped to the authenticated user and mentions the Moodle instance, but does not say what 'informações da instância' actually contains or whether the result is cached/session-dependent.

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 with no filler, immediately identifying the returned resources. Nothing is repeated from the title or annotations.

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 is the only source of return-value information, and it partially delivers by naming three user fields but leaves 'informações da instância do Moodle' as an unspecified bundle. For a simple identity/context tool this is adequate but not complete.

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 the schema carries no semantics to expand; the description correctly introduces no parameter discussion. Baseline of 4 applies for a 0-parameter tool.

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 description names a specific verb ('Retorna') and precise resources: the authenticated user and the UFSC Moodle instance, plus three concrete user fields (userid, nome completo, username). It is clear what the tool returns, though it does not explicitly contrast itself with look-alike siblings such as get_moodle_capabilities or get_courses.

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

Usage Guidelines2/5

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

There is no explicit statement of when to call this versus alternatives, nor any prerequisites (e.g., requires an authenticated session). The use case of identifying the current user is only implied by the phrase 'usuário autenticado'.

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