Skip to main content
Glama
aethis-mcp

aethis-mcp

Official
by Aethis-ai

aethis_discover_fields

Read-only

Discovers input fields from project source text and returns names, types, descriptions, and completeness so you can verify field consistency before writing test cases.

Instructions

Discover input fields from the project's source text. Returns field names, types, descriptions, and completeness assessment. Run this BEFORE writing test cases to ensure field names are consistent. Call repeatedly with aethis_refine_fields to improve completeness.

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

Input Schema

NameRequiredDescriptionDefault
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?

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, and the description is consistent with a non-mutating discovery call. It adds the useful note that repeated invocation alongside aethis_refine_fields progressively improves completeness, which indirectly explains the idempotentHint=false annotation, but says nothing about cost, latency, or what the 'completeness assessment' actually reports.

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, front-loaded sentences: purpose, return shape, then workflow ordering. Every sentence carries information; only the return-value sentence could be trimmed since no output schema exists but the payload is lightly summarized.

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 no output schema, the description correctly spends words on return contents and on the sequencing with aethis_refine_fields, which is the key thing an agent needs to order calls. It is still thin on what 'completeness' means numerically and does not acknowledge the credential parameters that make this call unusual for a read-only discovery tool.

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 sensitive anthropic_key variants is documented in the schema itself. The description only implies project_id via 'the project's source text' and adds no syntax, format, or credential-handling guidance beyond the schema — 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 verb and resource ('Discover input fields from the project's source text') and enumerates the return payload (field names, types, descriptions, completeness). The resource 'input fields' is naturally distinct from siblings like aethis_discover_rulesets and aethis_discover_sections, though the description never explicitly contrasts itself with them.

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 concrete ordering guidance ('Run this BEFORE writing test cases') and names the companion tool for iteration ('Call repeatedly with aethis_refine_fields'). It lacks any explicit when-not-to-use or selection criteria versus the other aethis_discover_* tools, which keeps it below a 5.

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