Skip to main content
Glama

面灵AI 面试助手

mark_job_application_failed

把一条投递标记为本次未投出,并写明原因(登录失效、对方报错、被拦截等)。回包为读回的状态。(需要用户授权,范围 job_applications:write)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "applicationId": "<applicationId>",
      "reason": "<reason>"
    },
    "name": "mark_job_application_failed"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYes未投出的原因
applicationIdYes投递记录 ID,从 list_job_applications 或加入清单的工具回包取得

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?

Adds real context beyond the annotations: the call requires user authorization with scope job_applications:write, and the response is a read-back status rather than a bare acknowledgement. Annotations already cover the non-read-only, non-destructive profile, so this is solid supplementary disclosure.

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?

Three compact clauses: action, reason examples, response and auth note. Front-loaded with the operation and free of filler, though the parenthetical auth note 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?

For a two-parameter mutation with no output schema, the description covers the action, valid reason categories, the authorization requirement, and the return shape. Nothing essential for correct invocation appears to be missing.

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 100%, so both parameters are already documented, including that applicationId comes from list_job_applications or the add-to-list tools. The description's example reasons add modest meaning to the reason field but nothing beyond the schema baseline.

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?

States a specific verb and resource (mark one job application as not submitted in this attempt) plus the accompanying reason. It distinguishes this from mark_job_application_submitted by the outcome state, though it never names that sibling explicitly.

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?

Concrete failure scenarios are given (login expired, counterpart error, blocked), which tells the agent when this applies. It does not distinguish this from abandon_job_application or say when to prefer either, so the routing guidance is only implied.

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