Skip to main content
Glama
aethis-mcp

aethis-mcp

Official
by Aethis-ai

aethis_generate_and_test

Generates rules from source text and runs all test cases, polling until completion, then returns pass/fail results with regression detection.

Instructions

Generate rules from source text and run all test cases. Triggers generation, polls until complete, then runs tests. Returns pass/fail with regression detection. Usually takes 60-120 seconds; if polling times out, use aethis_generation_status before retrying, and aethis_cancel_generation only when the caller wants to stop the run.

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_generate_and_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNoOptional authoring model
thinkingNoPer-generation thinking: disabled, adaptive, or enabled:N. Omit or null to inherit.
openai_keyNoRetired and refused: OpenAI credentials are not accepted for authoring.
project_idYesThe project ID
anthropic_keyNoAn Anthropic API key the user explicitly provided for this call. [sensitive — do not echo or log] Deprecated: the raw value is written verbatim to the host's session transcript. Never fill this from the environment.
deepseek_key_envNoOptional. For deepseek-flash only: must equal the variable explicitly configured in AETHIS_DEEPSEEK_KEY_ENV. Ambient provider keys are never read.
anthropic_key_envNoOptional. Only honoured when it equals the env var the user configured via AETHIS_ANTHROPIC_KEY_ENV in this MCP server's config; that configured key is used automatically, so this can be omitted. Do not guess a variable name: the server refuses any name the user did not configure.
anthropic_key_keychainNomacOS keychain reference the user created for Aethis: either 'service:account' or just 'account' (service defaults to 'aethis-anthropic-key'). The server reads it via the `security` command at call time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.23.0
    • addedInput schema / properties / deepseek_key_env
      Added value: +{
      +  "description": "Optional. For deepseek-flash only: must equal the variable explicitly configured in AETHIS_DEEPSEEK_KEY_ENV. Ambient provider keys are never read.",
      +  "type": "string"
      +}
    • addedInput schema / properties / model
      Added value: +{
      +  "description": "Optional authoring model",
      +  "enum": [
      +    "claude-sonnet-5",
      +    "deepseek-flash"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / openai_key / description
      Previous value: -"Retired and refused: Aethis LLM tools use Anthropic models only."New value: +"Retired and refused: OpenAI credentials are not accepted for authoring."
    • addedInput schema / properties / thinking
      Added value: +{
      +  "description": "Per-generation thinking: disabled, adaptive, or enabled:N. Omit or null to inherit.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  2. First observedv0.22.0

TDQS

A4.2/5.0
Behavior4/5

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

Adds substantial context beyond the annotations: a 60-120 second duration, internal polling semantics, a timeout recovery path, and the shape of the result ('pass/fail with regression detection'). Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so this is additive rather than load-bearing. It does not disclose whether a run consumes credits or what happens to existing rules on regeneration.

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?

Three sentences, front-loaded with the action and the pipeline, then the return value, then the failure/recovery guidance. No filler or restatement of the title; each sentence carries distinct information.

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 an 8-parameter, non-idempotent, long-running open-world operation with no output schema, the description covers duration, async behavior, result shape, and timeout handling. Minor gaps: it never explains where 'source text' comes from (no such parameter exists), and the deprecated/retired credential parameters (openai_key, anthropic_key) are only warned about in the schema.

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 every parameter including the credential/env/keychain options is already documented in structured form. The description mentions no parameter at all, so it adds no meaning beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 compound verb+resource: 'Generate rules from source text and run all test cases', then spells out the internal sequence (trigger, poll, run tests). This is clearly distinguishable from aethis_generation_status (polling only) and aethis_cancel_generation (abort only), which the description names by contrast.

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?

Explicit conditional routing: on polling timeout use aethis_generation_status before retrying, and use aethis_cancel_generation 'only when the caller wants to stop the run'. That is real when-to-use/when-not guidance with named alternatives. It stops short of saying when to prefer this combined generate+test call over a bare generation plus aethis_set_tests path.

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