Skip to main content
Glama

Aethel: AI interview facts and free practice

What one company's own pages say about its AI interview

get_company_interview
Read-onlyIdempotent

What one company's own pages say about its AI interview (length, format, retakes, recording, rules and more), topic by topic, each with the company page it rests on and the day it was read, then what those pages do not say, Aethel's page on the company and the free practice. An unknown name answers with the names Aethel has.

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": {
      "company": "<company>"
    },
    "name": "get_company_interview"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoen (the default) for English, es for Latin American Spanish.
companyYesThe company name, for example "Mercor", "HireVue" or "HackerRank".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description goes further by disclosing the shape of what comes back – per-topic facts each tied to a source page and a read date, an explicit gaps section, and the unknown-name resolution behavior – which is genuinely useful given there is no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single dense run-on sentence, and the tail ('then what those pages do not say, Aethel's page on the company and the free practice') reads as a comma-spliced fragment list rather than clear prose. The core scope is front-loaded, but the packaging costs readability.

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 carries the burden of explaining returns and does so adequately by listing content sections and the unknown-name case. Minor gaps remain: 'Aethel's page on the company' and 'the free practice' are never explained, leaving some return content ambiguous.

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 both parameters are already documented, including the en/es enum for lang. The description adds real meaning for company by stating that an unrecognized name yields the names Aethel knows, but says nothing about lang or accepted name formats beyond what the schema provides.

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 the resource precisely – one company's own pages about its AI interview – and enumerates the facets returned (length, format, retakes, recording, rules). It lacks an explicit verb and never names the sibling list_company_interviews as the multi-company alternative, so differentiation is implied rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance relative to list_company_interviews or compare_across_companies. The only usage rule given is the fallback for an unknown name (returning names Aethel has), which is a behavior, not selection guidance.

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