Skip to main content
Glama
aethis-mcp

aethis-mcp

Official
by Aethis-ai

aethis_refine_sections

Adds feedback guidance to refine section discovery and immediately re-runs discovery when sections are missing, mis-split, or misnamed.

Instructions

Add guidance to improve section discovery, then re-discover sections. Use when sections are missing, incorrectly split, or named differently than expected. Saves the feedback as a domain-level guidance hint and immediately re-runs discovery so you can see the effect. Repeat until the section list matches your expectations.

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": {
      "domain": "<domain>",
      "feedback": "<feedback>",
      "sources": "<sources>"
    },
    "name": "aethis_refine_sections"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain identifier, e.g. 'uk_citizenship'
sourcesYesThe same source documents used in the initial aethis_discover_sections call
feedbackYesWhat was wrong and how to fix it, e.g. 'The english language and life in the UK test should be separate sections'
openai_keyNoRetired and refused: OpenAI credentials are not accepted for authoring.
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.
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. Changed1 schema field changedv0.23.0
    • 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."
  2. First observedv0.22.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=false, openWorldHint=true and idempotentHint=false, and the description usefully adds that feedback is persisted as a domain-level guidance hint and that discovery is immediately re-run, which is the key side effect. It leaves unstated whether successive calls accumulate or overwrite prior hints, and does not flag that each call incurs a fresh discovery pass.

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?

Four tight sentences with the action front-loaded, followed by the trigger condition, the side effect, and the iteration loop. Nothing is redundant, though the second and fourth sentences both address iteration and could be consolidated.

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 7 parameters (4 of them credential variants), no output schema, and an open-world non-idempotent profile, the description still conveys the essential contract: send feedback, get a fresh section list back. What the re-discovered output actually contains is only implied by 'so you can see the effect', and the credential parameters are left entirely to 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 coverage is 100%, so every parameter including the auth-key variants is already documented in the schema. The description's only added semantic is that `feedback` persists at domain scope rather than being a one-shot instruction, which does shape how the agent should phrase it. Baseline 3 is appropriate 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific compound operation: adding guidance and then re-running section discovery, which is a distinct behavior from the sibling aethis_add_domain_guidance (add only) and aethis_discover_sections (discover only). An agent can tell what it produces without opening the schema, though no sibling is named explicitly.

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?

It gives a clear trigger condition: 'Use when sections are missing, incorrectly split, or named differently than expected', plus iterative guidance ('Repeat until the section list matches your expectations'). It stops short of stating when not to use it or how it differs from the plain add-guidance and discover tools.

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