Skip to main content
Glama

example_led_chaser

Destructive

Creates a new 12MHz 12T 8051 project containing an active-low 8-LED circuit on P1 and a C51 main.c file for LED chaser simulation.

Instructions

Create a NEW 12MHz 12T 8051, P1 active-low 8-LED circuit and C51 main.c.

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": {
      "project": "<project>"
    },
    "name": "example_led_chaser"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYes

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?

The annotations already declare readOnlyHint=false and destructiveHint=true, so the agent knows this mutates state; the description adds no context about what is destroyed, whether existing main.c or project contents are overwritten, or where files land. 'NEW' arguably softens the destructive signal without explaining it, leaving the destructiveHint unexplained for a create-style tool. With annotations present the bar is lower, but nothing here covers overwrite/collateral behavior.

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?

One front-loaded sentence with zero filler and the key hardware constraints packed in. It is terse to the point of omitting the parameter entirely, which is a completeness problem rather than verbosity, so structure itself is good.

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?

Placeholder correction-free assessment: a single-sentence create tool with no output schema and one undocumented parameter, silent on overwrite behavior and file location, is not complete enough for reliable invocation. The only partially mitigating factor is that the produced artifacts are described precisely.

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 coverage is 0% and the single required parameter 'project' is never mentioned in the description. The agent cannot tell whether 'project' is a new name, an existing project id, or a path, nor what happens if it already exists. The description must compensate here and does not.

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 names a concrete verb ('Create') plus the exact artifacts produced: a 12MHz 12T 8051 P1 active-low 8-LED circuit and a C51 main.c, with technical specifics (clock, core, port, polarity). That is far more specific than a generic 'create example'. It does not, however, explicitly distinguish itself from siblings such as native_export_led_chaser, so it stops short of a 5.

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 or when-not-to-use guidance, and no named alternative (e.g. native_export_led_chaser for exporting rather than creating, or native_create for generic creation). The word 'NEW' hints at additive intent but gives no prerequisites or selection criteria.

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