Skip to main content
Glama

run_sandbox_scenario

Read-onlyIdempotent

Load a named sandbox scenario and run the reconciliation pipeline in one call, returning an explainable match report for smoke tests and tolerance tuning.

Instructions

Load a named sandbox scenario and immediately return its reconciliation report.

Purpose: One-call execution that loads built-in fixture records and executes the reconciliation pipeline, returning a complete explainable match report.

When to use:

  • When performing quick verification, smoke tests, or initial agent demonstrations.

  • When verifying tolerance tuning against standard test cases.

When NOT to use:

  • Do NOT use with live production data.

  • Do NOT use when custom expected or observed records must be supplied; use reconcile instead.

Behavioral transparency: Deterministic, in-memory execution; read-only and idempotent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesScenario name, e.g. 'month_end'.
optionsNoOptional tuning object: 'abs_tol'/'rel_tol' (amount tolerance), 'date_window_days', 'high_threshold', 'review_threshold', 'currency_strict', 'enable_one_to_many', 'max_combination'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.2

TDQS

A4.4/5.0
Behavior4/5

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

Adds useful context beyond annotations: deterministic in-memory execution and built-in fixture records. However, 'read-only and idempotent' restates readOnlyHint/idempotentHint already present in the annotations, so the incremental value is partly redundant.

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?

Front-loaded purpose with clear section headers, and each bullet earns its place. The labeled 'Behavioral transparency' section partly duplicates the annotations, adding mild redundancy.

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

Completeness5/5

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

An output schema exists, so return-value detail is unnecessary. For a deterministic fixture-runner with full annotation and schema coverage, nothing an agent needs to invoke it correctly is missing.

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 coverage is 100%, so both 'name' and the tuning 'options' object are fully documented in the schema. The description adds no syntax or format detail beyond that, so the baseline 3 applies.

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?

States a specific verb (load) plus resource (named sandbox scenario) and the immediate effect (returns reconciliation report). The 'Purpose' line distinguishes it clearly from reconcile and load_sandbox_scenario.

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

Usage Guidelines5/5

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

Explicit when-to-use bullets (smoke tests, tolerance tuning) and when-not-to-use bullets (no live data, no custom records), naming the alternative tool 'reconcile' for the custom-records case.

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