Skip to main content
Glama
aethis-mcp

aethis-mcp

Official
by Aethis-ai

aethis_refine_fields

Adds field-extraction guidance and reruns discovery to correct missing, misnamed, or incomplete fields and enum values.

Instructions

Add guidance to improve field discovery, then re-discover. Use when fields are missing, misnamed, or enum values are incomplete. Adds a field_extraction guidance hint and re-runs discovery.

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>",
      "feedback": "<feedback>"
    },
    "name": "aethis_refine_fields"
  }
}

Input Schema

NameRequiredDescriptionDefault
feedbackYesGuidance about missing or incorrect fields (e.g., 'Section 7 implies a criminal record check')
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.
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?

Beyond the annotations it discloses that discovery is re-run, which is the key side effect. However, given openWorldHint=true and idempotentHint=false, it never warns that each call triggers an expensive re-discovery pass, that guidance may accumulate across calls, or that a configured Anthropic key may be required — all significant behavioral facts the schema hints at but the description omits.

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?

Three short sentences, trigger front-loaded, no preamble. The first sentence and the third restate the same add-then-rediscover idea, which is mild redundancy rather than noise.

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

Completeness3/5

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

For a non-idempotent, open-world mutation tool with six parameters including sensitive credential options, the description is adequate but thin: it covers what the tool does and when, not what an agent needs to know about cost, repeated invocation, or key configuration before calling.

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% and the field descriptions are unusually detailed (feedback examples, key-source rules, deprecation warnings), so the schema does the heavy lifting. The description adds nothing about parameter meaning beyond what is already there, so the baseline 3 applies.

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?

States a specific two-step action ('add guidance', 'then re-discover') scoped to field discovery, and names the mechanism ('field_extraction guidance hint'). This distinguishes it in practice from generic siblings like aethis_add_guidance and aethis_refine, 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?

Gives a clear trigger condition: 'Use when fields are missing, misnamed, or enum values are incomplete.' That is more concrete than most. It stops short of stating when NOT to use it or naming aethis_discover_fields / aethis_add_guidance as the alternative path.

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