Skip to main content
Glama

example_external_interrupt

Destructive

Create a C51 external-interrupt teaching circuit and source with buttons, LEDs, display, and buzzer. Use level and nesting modes to demonstrate interrupt priority, preemption, and boundary tests.

Instructions

Create a NEW C51 teaching circuit/source for external interrupts: two BUTTON inputs, 8 LEDs, multiplexed 4-digit CC display and transistor-driven buzzer. mode=level: idle chaser, held low-level input increments with alarm; mode=nesting: low-priority INT0 chaser can be preempted by high-priority INT1 increment. Diagnostic nets expose ISR activity/increment/wrap. initial_count defaults to 0000; other values support explicit boundary tests. Build/export/open/observe separately. Not physical driver or audio certification.

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_external_interrupt"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo
projectYes
initial_countNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=false, so the safety baseline is supplied. The description adds useful domain behavior: mode semantics, diagnostic nets, initial-count boundary testing, and the caveat that this is not a physical driver or audio certification. However, it does not explain what the destructive behavior actually affects, such as whether an existing project is overwritten, which is the key missing behavioral detail for a create tool marked destructive.

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?

The description is front-loaded with the create action and then supplies mode behavior, diagnostics, defaults, and scope limits. It is dense but mostly earns its space; the main structural weakness is that it remains one long paragraph rather than separating mode semantics from operational caveats.

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

Completeness3/5

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

For a relatively complex creation tool with no output schema, the description covers purpose, modes, default values, diagnostics, and limitations well. It still omits the meaning or expected format of the required project parameter and does not say what the tool returns or what exactly is created, leaving meaningful gaps for safe invocation.

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 0%, so the description must carry parameter meaning. It explains both enum values for mode in detail and states that initial_count defaults to 0000 with other values useful for boundary tests, but the required project parameter is left completely undefined.

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?

The description uses a specific verb, 'Create', and a precise resource: a NEW C51 teaching circuit/source for external interrupts. It distinguishes this from a generic LED chaser by naming the two-button, 8-LED, 4-digit display and buzzer setup, so an agent can identify the tool without opening the schema.

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 gives clear context for the two modes and explicitly says build, export, open, and observe happen separately, which tells the agent not to expect those actions here. It stops short of naming sibling tools as alternatives, but the operational boundary is clear.

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