Skip to main content
Glama

AceRound AI Interview Copilot

get_job_apply_client_status

Read-only

Show the state of the Auto Apply app on the user's computer: whether it is online, which conversations are running and what each is doing, how many applications are running or queued in one-click apply, whether any employer is waiting for an SMS code, and the latest reply in the Skills conversation (the default target of send_job_apply_instruction). Requires the AceRound Auto Apply desktop app on the user’s computer to be signed in and open (running in the background after closing the window also works); if the app is offline or outdated, the tool says so. (Requires the user's sign-in with scope job_applications: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": "get_job_apply_client_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/non-destructive/closed-world, and the description adds substantial context on top: the desktop-app dependency, the fact that background-running counts as available, the explicit failure behavior when the app is offline or outdated, and the required auth scope (job_applications:read). This is exactly the operational context an agent needs before calling and interpreting the result.

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?

Content is front-loaded with the purpose before prerequisites, and every clause carries information (states reported, dependency, failure behavior, auth scope). It is delivered as one very long sentence with stacked parentheticals, which slightly hurts scannability and could have been split into two or three sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description bears the burden of describing return values, and it does so by enumerating the reported states. Combined with the dependency, failure-mode, and auth disclosures, an agent has everything needed to call the tool and interpret the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter meaning to convey and the baseline of 4 applies. The description correctly spends its words on returned state rather than inventing argument semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ("Show the state of the Auto Apply app on the user's computer") and then enumerates exactly what state is reported: online status, running conversations and their current activity, one-click apply counts, pending SMS codes, and the latest Skills conversation reply. That enumeration lets an agent distinguish it from siblings like get_live_session_status or get_sms_relay_status without opening any schema.

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?

It gives concrete preconditions and a usage context: the desktop app must be signed in and open (or running in the background), and the Skills conversation is named as the default target of send_job_apply_instruction, which signals this is the read-side companion to that write tool. It does not explicitly say when to prefer this over a sibling status tool, so it stops just short of full routing 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