Enhanced GeoGebra MCP

Overview Schema Source Related Servers Discussions Admin

Reset GeoGebra Session

ggb_reset

Reset a GeoGebra applet by clearing the construction or reverting to its initial state. Use newConstruction mode for a fresh start or reset mode to restore the original construction.

Instructions

Clear the construction or reset the applet to its initial construction.

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": {
      "sessionId": "<sessionId>"
    },
    "name": "ggb_reset"
  }
}

Input Schema

Name	Required	Description	Default
`mode`	No		newConstruction
`sessionId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 31, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It implies a destructive clear/reset but does not mention reversibility, effects on undo history, session state, or any prerequisites. The mode-specific behavior is not explained.

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, front-loaded sentence with no wasted words. It efficiently communicates the core action, though the brevity contributes to under-specification elsewhere—an issue of completeness, not conciseness.

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 has 2 parameters, no output schema, and no annotations, the description is far too skeletal. It omits parameter semantics, mode differences, session context, and return/effect behavior. An AI agent would not have enough information to invoke the tool correctly.

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

Parameters1/5

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

Schema description coverage is 0%, so the description must compensate by explaining parameters. It does not mention 'sessionId' or 'mode' at all. The description only indirectly hints at two actions via 'clear' and 'reset', which map to the mode enum, but it fails to provide any semantic link or detail.

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 tool clears or resets a GeoGebra construction/applet, using specific verbs ('clear', 'reset') and a resource ('construction', 'applet'). It is distinguishable from sibling tools like ggb_create_session or ggb_eval_command, though it doesn't explicitly name alternatives.

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?

No guidance is given on when to use this tool versus alternatives, or when to choose 'newConstruction' versus 'reset' mode. The description simply states what it does without contextual usage directions.

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

Deploy Server