Skip to main content
Glama

面灵AI 面试助手

mark_job_application_submitted

Destructive

把投递清单中的一条标记为已投递(用户已在对方页面完成提交)。这一家此前未扣过网申家数时扣 1 家,不限家数期内不扣。回包为读回的状态。会消耗用户的时长、次数或产生付款,执行前向用户说明扣费内容并取得同意。(需要用户授权,范围 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>"
    },
    "name": "mark_job_application_submitted"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations, which already mark the operation as destructive, the description discloses quota-deduction logic: deduct one quota if this employer has not previously deducted one, and deduct nothing during an unlimited-quota period. It adds billing or duration consumption, the need to explain charges and obtain consent before execution, the read-back response shape, and the required auth scope. That is substantially more behavioral detail than the annotations provide.

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 main action is stated first, followed by the quota rule, the response, the billing and consent requirement, and finally the authorization scope. Each sentence adds useful information, and none repeats the name or title. It is dense but mostly free of filler.

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 single-parameter mutation with no output schema, the description covers the state change, the quota side effect, the consent and billing requirement, the authorization scope, and what the response will be. The description is complete enough for an agent to call it correctly and warns about the side effect.

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?

There is only one parameter, and the schema covers it fully (100%). The schema already explains that the applicationId comes from list_job_applications or an add-to-list tool, so the description adds no further meaning to the parameter semantics. The baseline 3 is appropriate.

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 description names a specific verb and resource: it marks one entry in the application list as submitted, and it clarifies that the user has already completed the submission on the other party's page. It does not explicitly distinguish this tool from the sibling tools mark_campus_job_submitted or record_submitted_job, so the scope boundary is left to the reader to infer.

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?

The description states when to call it: it applies only after the user has actually completed the submission on the counterparty's site. It also sets out a precondition requiring consent and an authorization scope. It does not mention any alternative tools or exclusions, such as when to use mark_job_application_failed or abandon_job_application.

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