worldparts

Overview Schema Source Related Servers Discussions Admin

run_contracts

Read-only

Run a component's scenarios and contracts to validate expected results, monotonicity, bounds, conservation, and warning conditions against the reference implementation.

Instructions

Run a component's scenarios and contracts and report pass or fail.

Scenarios have expected results; contracts check monotonicity, bounds, conservation and warning conditions against the reference implementation.

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": {
      "component": "<component>"
    },
    "name": "run_contracts"
  }
}

Input Schema

Name	Required	Description	Default
`component`	Yes	Full id or short alias.

Output Schema

Name	Required	Description	Default
`passed`	Yes
`component`	Yes
`contracts`	Yes
`scenarios`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 24, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=trueтные; the description adds value by explaining what contracts check and that evaluation is against the reference implementation. It does not contradict annotations or mention side effects, which is acceptable given the read-only hint.

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?

Two tightly scoped sentences: the first states the action and result, the second clarifies the underlying test categories. No filler or redundant restatement of the tool 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?

With one required parameter, full schema coverage, an output schema, and read-only annotations, the description supplies enough behavioral context to invoke the tool correctly. It could slightly improve by addressing when to prefer this over sibling checking tools, but that gap is not critical.

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?

The input schema already provides 100% coverage for the single parameter with 'Full id or short alias.' The description adds no additional parameter-level detail, so it meets but does not exceed the baseline.

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 states a specific action ('run'), a clear resource ('a component's scenarios and contracts'), and a concrete outcome ('report pass or fail'). It further distinguishes itself from validation/checking siblings by detailing what contracts verify (monotonicity, bounds, conservation, warning conditions against the reference implementation).

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?

The description implies the tool is for testing a component's scenarios and contracts)Skip. It doesn't explicitly state when to use this over siblings like check_system or compare_with_wntr, nor does it mention exclusions or alternatives.

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