Skip to main content
Glama

面灵AI 面试助手

preview_job_application_form

Read-only

投递前确认:查看岗位库中某个岗位的申请表,按用户的网申档案与简历预填了哪些内容、还缺哪些必填项。不投递、不扣费;开放题在投递时才由 AI 作答。(需要用户授权,范围 job_applications:read)

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

Input Schema

NameRequiredDescriptionDefault
campusJobIdYes岗位 ID,从 search_campus_jobs 取得

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 readOnlyHint=true annotation, the description adds real behavioral context: no submission occurs, no fees are charged, AI-written answers for open questions are deferred to submission time, and the call requires user authorization with the job_applications:read scope. These are exactly the facts an agent needs before calling a 'preview' tool that touches a paid application flow.

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 purpose is front-loaded in the first clause, followed by the return content, the no-side-effect guarantees, and the auth requirement in a compact form. Every clause carries information, though the parenthetical auth note could have been phrased more tightly.

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 read-only, single-parameter tool with no output schema, the description covers what would be returned (prefilled fields, missing required fields) along with safety and auth context. What remains thin is how the preview relates to the actual submission step, but nothing essential to correct invocation is 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 description coverage is 100% and the single campusJobId parameter is already documented as coming from search_campus_jobs. The description only adds that the job comes from the job library ('岗位库中某个岗位'), which is marginal meaning beyond the schema. 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 gives a concrete verb and resource ('查看岗位库中某个岗位的申请表') plus a precise scope ('按用户的网申档案与简历预填了哪些内容、还缺哪些必填项'), so an agent knows this is a pre-submission form inspection rather than a submission. It does not explicitly contrast with the existing get_job_application sibling, so the differentiation is by implication rather than by naming.

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?

Usage is clearly framed by the opening '投递前确认' — call this before submitting an application to check prefilled and missing fields. It also states when-not implicitly by clarifying '不投递、不扣费' and that open-ended questions are answered only at submission. No alternative tool is named, which keeps it shy of a 5.

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