Skip to main content
Glama
Sign In
Enhanced GeoGebra MCP

Enhanced GeoGebra MCP

by tiwe0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Evaluate CAS Expression

ggb_eval_cas

Evaluate a symbolic math expression in a GeoGebra CAS session to obtain the computed result.

Instructions

Evaluate a GeoGebra CAS expression in a session.

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>",
      "expression": "<expression>"
    },
    "name": "ggb_eval_cas"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYes
expressionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior1/5

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

With no annotations, the description carries the full burden. It does not disclose whether evaluation is read-only, whether it modifies session state, what the return format is, or any side effects. This is a significant gap for a tool that evaluates expressions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, which is concise, but it under-specifies the tool's behavior. Key information about parameters and effects is missing, making it more under-specification than effective conciseness.

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

Completeness1/5

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

Given the lack of annotations, no output schema, and minimal parameter details, the description is insufficient for an agent to understand how to invoke the tool correctly. It does not cover return values, error handling, or session prerequisites.

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 schema has 0% description coverage, so the description must compensate. It mentions 'expression' and 'session' but does not explain what a sessionId is, how to obtain it, or the expected format of the CAS expression. The description adds minimal meaning beyond the parameter names.

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 evaluates a GeoGebra CAS expression, which distinguishes it from sibling tools like ggb_eval_command (which likely evaluates a regular command). However, it does not explicitly mention the distinction, relying on the tool name.

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 provided on when to use this tool versus alternatives such as ggb_eval_command. The description implies it is for CAS expressions, but there is no explicit context or exclusions.

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