Skip to main content
Glama
aethis-mcp

aethis-mcp

Official
by Aethis-ai

aethis_set_bundle_contract

Idempotent

Stores a project's input invariants—consistency rules over inputs—to enforce them during generation and return field errors when decision inputs violate the contract.

Instructions

Store the bundle contract for a project: input invariants, which are author-declared consistency rules over the ruleset's inputs (for example member.renewal_date must not be before member.joined_date). Every later generation copies them into the compiled ruleset. When a decision's inputs break one, it returns undetermined with undetermined_reason input_errors and a field_errors message for each named field, and asks no further question; an invariant is skipped while any input it reads is missing. Each invariant is {id, expr, error_fields, message}: expr is exactly one comparison (=, !=, <, <=, >, >=) over field references and typed constants, and every error field must be read by it. At most 32 invariants. Replaces any stored contract; omit input_invariants, or pass null or [], to clear it. Field names and types are checked against the project's fields when generation starts. Use a test case's expectations.field_errors to assert the messages.

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_id": "<project_id>"
    },
    "name": "aethis_set_bundle_contract"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesThe project ID
input_invariantsNoInput invariants for the project: consistency rules over the ruleset's inputs, for example member.renewal_date must not be before member.joined_date. Omit, or pass null or [], to clear the stored contract.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.24.0

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important behavior: generation copies invariants into the compiled ruleset, broken invariants cause decisions to return undetermined with input_errors and field_errors, invariants are skipped when referenced inputs are missing, and field names/types are checked at generation time. It also explains replacement and clearing semantics.

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 core action and is information-dense, with no obviously wasted sentences. However, it is a single long paragraph covering purpose, runtime behavior, schema shape, limits, clearing, and testing advice, so some structural separation would improve readability.

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 mutation tool with no output schema, the description is largely complete: it explains the contract format, limits, clearing behavior, downstream effects, and error semantics. It does not describe any immediate tool response or authorization requirements, but those are relatively minor for this configuration-setting operation.

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 100%, so the structural details for input_invariants, expr, error_fields, and message are already documented in the schema. The description mostly restates those constraints in prose, adding only a small amount of meaning such as the generation-time field check, so the baseline of 3 is appropriate.

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 verb and resource: "Store the bundle contract" for a project, specifically its input invariants. It defines those invariants as author-declared consistency rules over the ruleset's inputs, which makes the tool's scope distinct from sibling tools that set field specs or tests.

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 detailed explanation of input invariants and their downstream effect on generation and decisions, but there is no explicit guidance on when to call this tool versus alternatives such as setting field specs or tests. The note about using test expectations.field_errors is helpful but is a testing instruction rather than a when-to-use rule.

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