Skip to main content
Glama

面灵AI 面试助手

get_job_apply_client_status

Read-only

查看用户电脑上网申客户端的现状:是否在线、哪些对话正在执行及各自在做什么、一键投递正在投与排队的家数、是否有公司在等短信验证码,以及 Skills 专用对话(send_job_apply_instruction 默认交给的那条)中网申 AI 最后说的话。需要用户电脑上的「面灵求职网申助手」客户端已登录并打开(关闭窗口后转入后台运行的同样可以);客户端不在线或版本较旧时,工具如实返回原因。(需要用户授权,范围 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.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the client-side dependency, that a backgrounded client is acceptable, that failures are reported truthfully with a reason, and that the job_applications:read scope is required. Only the exact shape of the returned status payload is left implicit.

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?

The verb and resource are front-loaded, and the enumeration of reported states is dense but each item is informative. The trailing parentheticals on client availability and authorization are useful rather than filler, though the single long sentence is somewhat heavy to parse.

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?

With no output schema, the description carries the burden of describing return content, and it does so by listing every reported state. It also covers prerequisites, degraded-mode behavior, and the required auth scope, leaving nothing an agent needs in order to call it correctly.

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 semantics to explain and the baseline of 4 applies. The description correctly spends no space on arguments and instead describes the returned state.

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+resource (查看…网申客户端的现状) and then enumerates exactly what is reported: online state, running conversations and their current activity, one-click apply counts, SMS-code waiting, and the last AI message in the Skills conversation. This is far more specific than the sibling names alone and lets an agent distinguish it from get_live_session_status or get_sms_relay_status.

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 states the precondition for use clearly: the '面灵求职网申助手' client must be logged in and open, and a backgrounded (window-closed) client still counts. It also explains the fallback when the client is offline or outdated. It does not explicitly route the agent to an alternative tool for overlapping status queries, which keeps it below a 5.

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