beebjit-mcp

by acscpt

Overview Schema Source Related Servers Discussions Admin

Python

Local

run_basic

Run a BBC BASIC program on an emulated BBC Micro and return the final MODE 7 screen as rows and text for assertion.

Instructions

Type a BBC BASIC program, RUN it, and return the final screen.

Convenience wrapper around type_input + cycle runs. program is the full BASIC source; each line must carry its own line number (this tool does not auto-number). A leading NEW is issued first so the program runs in a clean workspace.

boot_cycles gives BASIC time to reach the prompt after NEW; settle_cycles is the max BBC cycle budget for the program's own execution after RUN.

Returns the MODE 7 screen as rows (list of 25 lines) and text (newline-joined) so callers can assert on either shape.

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": {
      "session_id": "<session_id>",
      "program": "<program>"
    },
    "name": "run_basic"
  }
}

Input Schema

Name	Required	Description	Default
`program`	Yes
`session_id`	Yes
`boot_cycles`	No
`settle_cycles`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Jul 31, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Since no annotations are provided, the description carries the full burden. It discloses key behaviors: issuing `NEW`, requiring line numbers, boot/settle cycle budgets, and returning rows/text. It does not detail error handling or timeout behavior, which is a gap.

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 well-organized. It front-loads the core purpose, then explains parameters and return values in separate sentences. Every sentence contributes useful information without redundancy.

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?

Given 4 parameters and an output schema, the description covers the main workflow, parameter meanings, and return format. It lacks explicit error/timeout behavior, but the overall completeness is high.

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

Parameters5/5

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

The description adds meaning to all key parameters: `program` (full source, no auto-numbering), `boot_cycles` (time for NEW-to-prompt), and `settle_cycles` (max execution budget). It also explains the output shape. The schema has 0% coverage, so this description is essential and thorough.

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 opens with a specific, actionable statement: 'Type a BBC BASIC program, RUN it, and return the final screen.' It clearly identifies the tool as a convenience wrapper around type_input and cycle runs, distinguishing it from sibling tools like type_input or run_for_cycles.

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?

The description explains that this is a convenience wrapper around `type_input` + cycle runs, which implies the manual alternative. It does not explicitly list exclusions or when to prefer other run tools, but the context is clear.

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