Skip to main content
Glama
Sign In
Chalkcast

Chalkcast

by FredMichel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

open_project

Starts a Manim animation project session with configurable quality, theme, and frame rate so you can author and render scenes from a concept.

Instructions

Start a project session. quality: draft|low|medium|high. theme: chalkboard|whiteboard|dark.

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

Input Schema

NameRequiredDescriptionDefault
fpsNo
themeNochalkboard
qualityNolow

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and discloses almost nothing: it doesn't say a session is created/held, whether state persists until close_project, whether calling twice is an error, or how fps affects output. Only the two enumerations add real information.

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?

Front-loaded and free of filler; the key action comes first followed by the two enumerations. The telegraphic 'quality: draft|low|medium|high' style is terse but parseable, and nothing superfluous is included.

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?

An output schema exists so return values needn't be described, but for a stateful session-opening tool with zero annotations and 0% schema coverage, the description omits the lifecycle contract, the meaning of defaults, and the fps parameter entirely.

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 coverage is 0%, so the description is the only source of parameter meaning, and it supplies value domains for quality and theme that the schema lacks (schema declares them as free-form strings with no enums). However, 'fps' is never mentioned and no defaults or effects of quality/theme are explained.

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?

'Start a project session' gives a clear verb and resource, and 'open' vs the sibling 'close_project'/'inspect_project' is self-evident. It never explicitly distinguishes itself from those siblings, but the intent is unambiguous.

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 on when to call it, whether it must precede add_scene/add_equation, whether an existing session must be closed first, or what happens if one is already open. The agent has to infer the whole session lifecycle from sibling names.

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