Skip to main content
Glama

面灵AI 面试助手

stop_job_apply_task

停止网申 AI 正在做的事,与用户在客户端点「停止」相同:传 taskId 只停这条对话(一键投递中的一家同时移出本轮);不传时等同于投递清单的「全部停止」(正在投的立即停止、排队中的不再投递),并停下其余正在执行的对话。已填写的页面保留,之后可用 send_job_apply_instruction 让它接着做。回包为停止后读回的状态。需要用户电脑上的「面灵求职网申助手」客户端已登录并打开(关闭窗口后转入后台运行的同样可以);客户端不在线或版本较旧时,工具如实返回原因。(需要用户授权,范围 job_applications:write)

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

Input Schema

NameRequiredDescriptionDefault
taskIdNo对话 ID(taskId),从 get_job_apply_client_status 取得

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations (readOnly=false, destructive=false, openWorld=false), the description discloses that filled form pages are preserved and resumable, that the response is the state read back after stopping, that it requires a logged-in client (including background-running), and that it fails with an honest reason when the client is offline or outdated. It also declares the authorization scope job_applications:write. Nothing here contradicts the non-destructive annotation, since state is retained.

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 definition is front-loaded with the core action and the Stop-button analogy, then layers conditions and failure behavior in roughly descending importance. It is dense but nearly every clause carries distinct operational information; the parentheticals make it slightly heavier than necessary.

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?

For a mutation tool with no output schema, prerequisites (client online and logged in, version currency), authorization scope, scope of effect for both modes, preserved state, follow-up path, and return semantics are all covered. An agent has everything needed to decide, call, and interpret the result.

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?

Schema coverage is 100% and the single parameter is optional, so the schema already carries the basic semantics; the description goes further by defining what a null taskId means globally and what removing a company from the current round implies. It does not add format or length constraints, but that is already covered by the schema.

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 names a concrete verb and object ('stop what the job-apply AI is doing') and immediately anchors it to a familiar user action (clicking Stop in the client), then splits the behavior into two distinct modes (with and without taskId). An agent can tell this apart from siblings like send_job_apply_instruction or abandon_job_application 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 Guidelines5/5

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

It states explicitly when to pass taskId (stop only that conversation, plus its company is removed from the current one-click round) versus omitting it (global 'stop all', halting applying and queued items plus other running conversations). It also names the follow-up alternative send_job_apply_instruction for resuming later, which is exactly the routing guidance an agent needs.

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