Skip to main content
Glama
Sign In
math-board

math-board

by smdesai27
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Board reference

board_docs
Read-onlyIdempotent

Look up blackboard artifact formats, examples, marks, equations, chapters, camera, animation, layout, styles, and saves before using a format for the first time.

Instructions

Reference for the blackboard: artifact formats with examples (plot, svg, mermaid, molecule, icon), marks, equations, chapters and camera, animation, layout and style, saves. Call it before using a format for the first time.

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": {
      "topic": "<topic>"
    },
    "name": "board_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYesoverview lists what you can draw

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.8/5.0
Behavior3/5

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

The readOnlyHint, idempotentHint, non-destructive, and closed-world annotations already establish the safety profile. The description adds useful context about the reference contents and first-use guidance, but it does not describe the return format or depth of examples, so it adds moderate value beyond the annotations.

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 compact and front-loaded: it names the resource, enumerates key content areas, and ends with a clear usage instruction. Every sentence adds useful information without padding.

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 simple one-parameter reference tool with a fully documented enum and existing annotations, the description provides enough context to understand its purpose and when to call it. It omits a few enum topics such as workflow and html, but the schema exposes them directly and no output schema needs explanation.

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

Parameters3/5

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

Schema description coverage is 100%, and the single topic parameter is an enum with a description for overview. The description lists several reference topics that map to enum values, but it does not explain how to choose among topics or cover every enum option, so the schema remains the primary source of parameter meaning.

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 identifies this as a reference tool for blackboard artifact formats and lists concrete topics such as plot, svg, mermaid, marks, equations, animation, layout, and saves. It is distinguishable from action-oriented siblings like board_update or board_save, though it does not explicitly name those 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?

It explicitly says to call it before using a format for the first time, giving a clear trigger for use. It does not describe when not to use it or name an alternative tool, so it falls short of the top score.

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