Skip to main content
Glama

get_quizzes

Retrieve the list of quizzes from a configured Moodle course to manage assessments and track student progress.

Instructions

Obtiene la lista de quizzes en el curso configurado

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'get_quizzes' tool. It calls the Moodle Web Service 'mod_quiz_get_quizzes_by_courses' to fetch quizzes for the configured course and returns them as JSON string.
    private async getQuizzes() {
      console.error('[API] Requesting quizzes');
      
      const response = await this.axiosInstance.get('', {
        params: {
          wsfunction: 'mod_quiz_get_quizzes_by_courses',
          courseids: [MOODLE_COURSE_ID],
        },
      });
    
      const quizzes = response.data.quizzes || [];
      
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(quizzes, null, 2),
          },
        ],
      };
    }
  • src/index.ts:146-154 (registration)
    Tool registration in the ListTools response, defining name, description, and empty input schema (no parameters required).
    {
      name: 'get_quizzes',
      description: 'Obtiene la lista de quizzes en el curso configurado',
      inputSchema: {
        type: 'object',
        properties: {},
        required: [],
      },
    },
  • TypeScript interface defining the structure of a Quiz object, used in the context of quiz data.
    interface Quiz {
      id: number;
      name: string;
      timeopen: number;
      timeclose: number;
      grade: number;
      timemodified: number;
    }
  • src/index.ts:247-248 (registration)
    Dispatcher in CallToolRequest handler that routes 'get_quizzes' calls to the getQuizzes() method.
    case 'get_quizzes':
      return await this.getQuizzes();
  • Input schema for the get_quizzes tool, specifying no required parameters.
    inputSchema: {
      type: 'object',
      properties: {},
      required: [],
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a retrieval operation ('obtiene'), implying read-only behavior, but doesn't specify whether it requires authentication, returns paginated results, has rate limits, or what format the list returns. For a tool with zero annotation coverage, this leaves significant behavioral 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?

The description is a single, efficient sentence in Spanish that directly states the tool's purpose. It's front-loaded with the core action and resource, with no redundant words or unnecessary elaboration. Every word earns its place in conveying the essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no output schema), the description is minimally adequate but incomplete. It doesn't explain what 'curso configurado' means (e.g., is this a pre-configured context or requires prior setup?), what the returned list contains, or any error conditions. For a tool with no annotations or output schema, more contextual detail would be helpful.

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 has zero parameters, and schema description coverage is 100% (since there are no parameters to describe). The description correctly indicates no parameters are needed by not mentioning any. With 0 parameters, the baseline is 4, as there's nothing additional to explain beyond what the empty schema already shows.

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 clearly states the action ('obtiene' - gets/retrieves) and the resource ('lista de quizzes en el curso configurado' - list of quizzes in the configured course). It distinguishes from siblings like 'get_assignments' and 'get_quiz_grade' by specifying quizzes rather than assignments or grades. However, it doesn't explicitly differentiate from other list operations beyond the resource type.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (like needing a configured course), when not to use it, or how it differs from similar tools like 'get_assignments' or 'get_submissions' beyond the resource type. The agent must infer usage from the tool name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cfsandoval/Mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server