Skip to main content
Glama

Aethel: AI interview facts and free practice

List the companies Aethel has an AI interview page for

list_company_interviews
Read-onlyIdempotent

Lists the 42 companies Aethel has a page on, for their AI interview: the company, who runs its interview as Aethel's page says (an AI, a person, or recorded questions), the page's address, and the day the company's own pages were read.

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": "list_company_interviews"
  }
}

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real value beyond them: the set is a fixed 42 companies, the attribution is reported as the page states it (an AI, a person, or recorded questions), and a data-freshness field records when the company's own pages were read.

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 front-loaded sentence that states the resource and scope before unpacking the returned fields, with zero filler. The colon-and-list construction makes it slightly run-on but every clause carries information.

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 usefully enumerates the returned fields (company, interviewer type, page address, page-read date), which is exactly what an agent needs to decide whether to call it. Remaining gaps are minor — no mention of whether unknown interviewer types occur or of ordering — for a tool with one optional, fully documented parameter.

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 optional `lang` parameter is fully described in the schema, including the enum values and the English default. The description says nothing about language selection or localization behavior, so it adds no meaning beyond the schema — baseline 3 applies at 100% coverage.

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 uses a specific verb ("Lists") plus a precise scope ("the 42 companies Aethel has a page on, for their AI interview") and enumerates the fields returned. It is clearly distinguishable from a single-record tool like get_company_interview by its plural, exhaustive scope, but it never explicitly names a sibling to contrast with.

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 implied: an agent can infer this is the entry-point enumeration for browsing company interview pages. There is no explicit statement of when to prefer this over get_company_interview or compare_across_companies, and no stated exclusions or prerequisites.

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