Skip to main content
Glama

Run a Lugh program's tests

lugh_test
Read-onlyIdempotent

Run the test blocks of a Lugh program in a sandbox to verify behavior and report passes and failures.

Instructions

Run the test blocks of a Lugh program in the sandbox and report passes and failures.

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": {
      "code": "<code>"
    },
    "name": "lugh_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesA complete Lugh program, starting with `agent <Name>`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed sandbox, so the safety profile is covered. The description adds that execution happens 'in the sandbox' and that results are reported as passes and failures, which is useful, but it does not say whether failing tests are returned as data or raised as an error, nor whether execution can time out.

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?

One sentence, front-loaded with the action and ending with the observable outcome. No redundant restatement of the title or name.

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?

For a one-parameter, read-only sandbox tool with full schema coverage and no output schema, the definition covers what it does and roughly what it returns. The main missing piece is failure semantics — whether a failing test suite is an error or a normal result.

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?

There is a single parameter with 100% schema description coverage, and the schema already specifies a complete program starting with `agent <Name>`. The description adds only the constraint that `test` blocks are the tested portion, which is minor incremental meaning over the schema — baseline 3 applies.

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 specific verb and resource (run the `test` blocks of a Lugh program) plus the scope (in the sandbox) and the result shape (passes and failures). That is enough to separate it from lugh_run, but it never explicitly says it is not running the program's main entry point, so sibling differentiation is only implied.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the verb 'test' — you call this when you want to verify a program's test blocks. There is no explicit when-to-use versus lugh_check (static checking) or lugh_run (execution), and no stated prerequisites such as the program needing test blocks.

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