Skip to main content
Glama

TrueInterview

List my applications

list_applications
Read-onlyIdempotent

The applications the candidate tracks on TrueInterview, most recently updated first, a page at a time, with a count for every status over the whole tracker (zeros included). Each row's status is the same word the status filter, track_application and update_application take (an interview carries interview_round). page.has_more says another page follows and page.total how many rows the filter covers. prepare_application already says whether a role is tracked, across every row. Each row's prep counts that employer's reported questions and interview notes.

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

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page.
limitNo
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's job is added context, and it delivers: newest-first ordering, page-at-a-time delivery, status counts computed over the whole tracker with zeros included, and the meaning of page.has_more/page.total. It does not mention rate limits or result-size ceilings, but the behavioral picture is substantially richer than the annotations alone.

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?

The core purpose is front-loaded, but the prose is dense and run-on, and the sentence about prepare_application ('already says whether a role is tracked, across every row') is grammatically awkward and easy to misread. Several clauses about return shape are justified by the absent output schema, but they could be tighter.

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 return-shape burden and largely succeeds: ordering, page envelope semantics, whole-tracker status counts, and the per-row prep meaning. The main gap is the 'limit' parameter and the page-size ceiling, plus whether counts are affected by the status filter – though 'over the whole tracker' implies they are not.

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 only 33%, so the description must compensate. It does well on 'status', explaining that rows use the same vocabulary the filter and track/update_application accept and that 'interview' rows carry an interview_round. It says nothing about 'limit' or the default/maximum page size, which the schema also leaves undocumented.

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 applications the candidate tracks on TrueInterview' names a specific resource and scope, and the description immediately qualifies it with ordering (most recently updated first) and pagination. It stops short of an explicit differentiating verb ('list'), but the intent is unambiguous.

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?

It implies one routing rule – that prepare_application, not this tool, is the way to check whether a role is tracked 'across every row' – and it ties the status filter vocabulary to track_application/update_application. There is no explicit when-to-use/when-not statement or a named alternative for browsing conversations or contacts.

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