Skip to main content
Glama
Sign In
Chalkcast

Chalkcast

by FredMichel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_area

Shade the area under a plotted function between x_min and x_max to visualize the integral in a Manim animation.

Instructions

Shade the area under a plotted function between x_min and x_max (the integral).

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": {
      "plot_id": "<plot_id>"
    },
    "name": "add_area"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorNoBLUE
x_maxNo
x_minNo
opacityNo
plot_idYes
scene_idNo
project_idNo
function_indexNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It says the tool shades an area, but does not disclose that it mutates an existing plot, what prerequisites exist (e.g., an existing plotted function), or any permission/reversibility considerations.

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 a single front-loaded sentence with no wasted words. It clearly leads with the operation and its key bounds.

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 an 8-parameter mutation tool with no annotations and no schema parameter descriptions, the definition is too thin. It does not explain how plot_id links the area to an existing plot or what function_index selects, leaving an agent with insufficient context to invoke it confidently.

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?

Schema description coverage is 0% across 8 parameters, and the description only explains x_min and x_max. It leaves the required plot_id, plus function_index, color, opacity, scene_id, and project_id undocumented in both schema and description.

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 states a specific action: shading the area under a plotted function between x_min and x_max, explicitly identifying it as the integral. This distinguishes it from generic plotting tools like add_plot or add_equation, though it does not name close siblings such as add_riemann or add_step.

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 explicit guidance on when to use add_area versus alternatives; the only usage cue is the implied integral visualization. It does not say when to choose this over add_riemann, add_step, or other plot annotations.

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