Skip to main content
Glama
Sign In
moodle_math_mcp

moodle_math_mcp

by tab11pm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_assignment_details

Opens a Moodle assignment page and retrieves the assignment text. Provide the assignment URL to access task details directly.

Instructions

Открыть страницу задания в math Moodle и вернуть текст задания

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "assignmentUrl": "<assignmentUrl>"
    },
    "name": "get_assignment_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
assignmentUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It does disclose that the tool opens a page and returns the assignment text, implying a read-like retrieval. However, it does not state whether it is read-only, what happens on failure, or whether any page session state is affected.

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, succinct sentence that front-loads the action and outcome. There is no filler, redundant phrasing, or unnecessary detail.

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 low-complexity tool with one required URL parameter and no output schema, the description is mostly sufficient: it identifies the input, the operation, and the return value. It could add notes about authentication or error behavior, but these are minor gaps for such a simple fetch-style tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage and the tool description does not mention the assignmentUrl parameter or explain its expected format. The property name and uri format are self-explanatory to some degree, but the description itself adds no parameter semantics beyond what the schema already provides.

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 states a clear action—'open the assignment page in math Moodle and return the assignment text'—and identifies a specific resource (the assignment page in math Moodle). It is not a tautology of the tool name and is distinct enough from sibling tools that handle course/file listing.

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 gives no explicit guidance about when to use this tool versus siblings such as list_courses or download_module_files. It only implies use when assignment text is needed, with no exclusions, prerequisites, or alternative routing.

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