Skip to main content
Glama

面灵AI 面试助手

get_job_application

Read-only

查看一条网申投递的详情:岗位信息(批次、类型、职位描述与要求、截止日期)与这次投递使用的简历。(需要用户授权,范围 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": {
      "applicationId": "<applicationId>"
    },
    "name": "get_job_application"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the required user authorization and the job_applications:read scope, plus what data is returned. It does not discuss error behavior or missing-record handling, so a 3 is fair.

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 compact sentence with the resource and returned fields front-loaded, followed by the auth/scope note in parentheses. No wasted wording, though the parenthetical could be split for scannability.

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?

No output schema exists, but the description enumerates the returned fields well enough for an agent to know what it gets. Auth and scope requirements are disclosed. Only minor gaps remain, such as behavior when the ID is invalid or not found.

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 applicationId parameter is fully documented in the schema, including where to obtain it. The description adds no parameter meaning beyond that, so the baseline 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?

States a specific verb (查看) and resource (一条网申投递的详情) and enumerates the returned content: batch, type, JD/requirements, deadline, and the resume used. The singular '一条' implicitly contrasts with the list sibling, though no sibling is named 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?

Usage is implied — fetch one application's detail — and the schema parameter note points to list_job_applications as the ID source. However, the description itself gives no explicit when-to-use/when-not guidance or named alternatives.

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