Skip to main content
Glama

Aethel: AI interview facts and free practice

Aethel's free AI interview practice

about_practice
Read-onlyIdempotent

What Aethel's free AI interview practice is (roles and levels, typed or spoken answers, an instant check that quotes the person's own words, no account, nothing saved), what the free full interview is (about 15 minutes, with an AI interviewer that says it is an AI), and the addresses.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "about_practice"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoen (the default) for English, es for Latin American Spanish.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: no account required, nothing stored, the interview is about 15 minutes, and the AI interviewer discloses that it is an AI. Only a minor gap remains (whether output is localized to `lang`).

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?

One sentence, front-loaded with the main subject and scoped by tight parentheticals; every clause carries content (product scope, full-interview length, disclosure, addresses). The stacked parentheticals make it dense, which keeps it from a 5.

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 simple static info tool with one optional enum parameter and no output schema, the description covers what is returned and the privacy/disclosure posture well. The only omission is any statement about how the `lang` parameter affects the returned content.

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?

The single `lang` parameter has 100% schema description coverage (en default, es for Latin American Spanish), so the schema carries the burden and baseline 3 applies. The description adds nothing about language, so it does not clarify whether the returned copy itself is localized.

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 states specifically what the tool returns: an overview of Aethel's free AI interview practice (roles/levels, typed or spoken answers, instant quote-based feedback, no account, nothing saved) plus what the free full interview is and the addresses. That is a concrete content inventory rather than a tautology. It does not explicitly distinguish itself from the sibling interview-data tools (get_company_interview, compare_across_companies, list_company_interviews), so it stops short of a 5.

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 only implied: the listed content topics suggest it answers 'what is this practice / how does it work' questions. There is no explicit when-to-use statement, no when-not, and no routing to or away from the sibling tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources