Skip to main content
Glama
MathMagic MCP Pro

MathMagic MCP Pro

by mrtersn9-cpu

mathmagic_policy

Retrieves MathMagic MCP Pro's operating policy: what it does and never does, supported modes, synchronization, and focus behavior, so you can verify background equation insertion constraints.

Instructions

What this server does and never does; modes, synchronisation and focus behaviour.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it says nothing about whether the call is read-only, whether it mutates server state, or what it costs. The phrases "does and never does" and "focus behaviour" hint that constraints exist but never state one, so the agent learns no concrete behavioral fact.

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

Conciseness4/5

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

It is a single compact clause with no filler and the scope words are up front. The terseness is efficient, though the noun-less phrasing makes it read more like a section heading than a tool description.

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?

For a zero-argument informational tool with no output schema, the description is the only place the agent can learn what comes back, and it only lists topic areas without saying what form the answer takes. With no annotations and no return-value documentation, key questions about calling it remain open.

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 and the schema is empty, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly adds no redundant parameter talk.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a topic fragment ("What this server does and never does; modes, synchronisation and focus behaviour") rather than a verb+resource statement. An agent can guess it returns policy documentation, but it never says so explicitly and offers nothing to distinguish it from the sibling mathmagic_capabilities, which plausibly covers the same ground.

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 when-to-use guidance, no prerequisite, and no named alternative. Given that mathmagic_capabilities sits alongside it, the absence of any routing cue leaves the agent to guess which of the two to call.

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