Skip to main content
Glama
Sign In
math-board

math-board

by smdesai27
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Open board

board_open
Idempotent

Open a shared blackboard to teach visually: starts it, displays it in the learner's browser, and activates drawing tools for equations, plots, and diagrams.

Instructions

Open the shared blackboard to teach visually: starts it, shows it in the learner's browser and activates the board tools (board_read, board_update, board_docs, ...). Returns the URL if no browser opens. Safe to call again.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.5/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing a real side effect the hints cannot express: the board opens in the learner's browser, which matters for a non-readOnly tool. It also gives the fallback behavior ('Returns the URL if no browser opens') and confirms idempotency in plain language. It leaves out what happens to pre-existing board content on re-open, which is the one thing an agent might still want.

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?

Two sentences, both front-loaded: the verb and effect first, the return-value caveat and idempotency note second. The colon-separated effect list packs three behaviors without wasted words, and there is no boilerplate.

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

Completeness5/5

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

With no parameters and no output schema, the description carries the return-value burden itself, and it does ('Returns the URL'). Side effect, tool activation, and re-call safety are all covered, so an agent has everything needed to invoke it correctly.

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?

Zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. Nothing in the description misleads about inputs.

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

Purpose5/5

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

States a specific verb and resource ('Open the shared blackboard') plus its teaching purpose, then enumerates the concrete effects: starting the board, showing it in the learner's browser, and activating the board tool set. Naming board_read/board_update/board_docs as things it activates makes it unmistakably the gateway tool relative to its siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'to teach visually' framing plus 'activates the board tools' implies this is the prerequisite call before the read/update/docs siblings, and 'Safe to call again' tells the agent repeat invocation is acceptable. It stops short of an explicit 'do not call board_read before this' or 'use X instead when Y', so it is clear context without 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