Skip to main content
Glama

面灵AI 面试助手

record_submitted_job

补录一条用户在别处已经投递过的岗位(手动填写公司与岗位),直接记为已投递并进入投递追踪,不扣网申家数。岗位库中的岗位用 mark_campus_job_submitted。(需要用户授权,范围 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": {
      "company": "<company>",
      "jobTitle": "<jobTitle>"
    },
    "name": "record_submitted_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
citiesNo工作城市(选填)
jobUrlNo岗位链接(选填)
companyYes公司名
jobTitleYes岗位名

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false), the description discloses two consequential behaviors: the record is immediately marked as submitted and enters tracking, and it does not consume the 网申家数 quota. It also states the required auth scope (job_applications:write). It does not cover duplicate/already-recorded handling or what the response contains, which keeps it off a 5.

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 core action and its quota behavior are front-loaded, and the sibling routing plus auth scope are placed afterward in parentheses, which reads well. It is dense but nearly every clause adds information; only the parenthetical fields restate the schema.

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 mutation tool with no output schema, the description covers purpose, the alternative path, the authorization requirement, and a non-obvious side effect (no quota deduction). The remaining gap is duplicate-handling behavior, which an agent would want before writing a record.

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 description coverage is 100%, so all four parameters are already documented in the schema, and the description only repeats that company and jobTitle are filled manually. Baseline 3 applies since the schema carries the parameter detail.

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 uses a specific verb+resource combination ('补录一条…岗位'), states the record is created as already-submitted and enters application tracking, and explicitly names the sibling tool (mark_campus_job_submitted) that handles the library-job case. An agent can distinguish this from the campus/library variants 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?

The description states exactly when to use it (the user applied elsewhere and the company/job must be entered manually) and gives an explicit alternative for a different case ('岗位库中的岗位用 mark_campus_job_submitted'). The selection condition is stated rather than inferred.

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