Skip to main content
Glama

面灵AI 面试助手

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": {
      "campusJobId": "<campusJobId>"
    },
    "name": "mark_campus_job_submitted"
  }
}

Input Schema

NameRequiredDescriptionDefault
campusJobIdYes岗位 ID,从 search_campus_jobs 取得

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the annotations (readOnly=false, destructive=false), the description discloses the actual write semantics: create a record if none exists, leave the submission timestamp untouched if already submitted (idempotent behavior), and no deduction of the application quota count. It also states the required authorization scope job_applications:write, which is exactly the operational context an agent needs before invoking a mutation.

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?

One dense sentence front-loads the core action, then packs edge-case behavior, quota semantics, and the auth scope into a parenthetical. Every clause carries information, though the run-on structure with nested punctuation makes it slightly harder to scan than a bulleted form would be.

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 single-parameter mutation with no output schema, the description covers the important unknowns: side effects, idempotency, quota impact, and authorization. The only notable omission is what the call returns or what happens on an invalid/unknown campusJobId, which would matter for error handling.

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%, and the single parameter already documents that the ID comes from search_campus_jobs. The description adds no further parameter meaning (no format, no validity constraints) beyond what the schema provides, so the baseline of 3 applies.

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 states a specific verb and resource: mark a job in the campus job library as already submitted elsewhere by the user. It scopes the resource ('岗位库中的一个岗位') which hints at the campus-library boundary, but it never names or contrasts with the closely related siblings such as mark_job_application_submitted or record_submitted_job, so an agent must infer which one applies.

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?

Usage is implied by the phrase '用户已在别处投递过' (the user already applied elsewhere), which is a usable trigger condition, but there is no explicit when-not guidance and no reference to an alternative tool for the in-platform submission path. The agent gets a workable condition but must reason about the sibling boundary itself.

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