Skip to main content
Glama

面灵AI 面试助手

update_job_intent

修改用户的求职意向:传入的维度整体替换原值(追加时传完整的新数组),未传入的不变。回包为读回的意向。(需要用户授权,范围 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": {
      "patch": "<patch>"
    },
    "name": "update_job_intent"
  }
}

Input Schema

NameRequiredDescriptionDefault
patchYes
markInterviewedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations declare a non-read-only, non-destructive, closed-world mutation; the description adds meaningful context beyond that: per-dimension replace-not-merge semantics, the required auth scope job_applications:write, and that the response is the read-back intent. It does not explain what markInterviewed does, which is the one notable omission.

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?

Dense and front-loaded: the replace semantics come first, then response shape, then the auth requirement in parentheses. Every clause carries information and nothing is padded, though the terse Chinese phrasing requires careful parsing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with a nested 9-field patch object, a markInterviewed flag, no output schema, and zero schema descriptions, the definition covers the essential operational rule and auth scope but leaves the field-level semantics and the markInterviewed flag unexplained. Adequate to avoid misuse of the patch mechanics, incomplete for the full parameter surface.

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 0%, and the nested patch object carries nine array fields with no per-field documentation. The description compensates for the most critical ambiguity by explaining whole-array replacement, but it says nothing about the individual dimensions (cities, batches, directions, companyScales, etc.) or the markInterviewed boolean, so a substantial semantic gap remains.

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 (修改用户的求职意向) and immediately clarifies the central semantics, whole-value replacement per dimension. It clearly contrasts with the read-only sibling get_job_intent by stating the response is the read-back intent, though it never names that sibling 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?

It conveys the key usage rule — pass the full new array when appending, omit dimensions to leave them unchanged — which governs how to call it correctly. However, it gives no explicit when-to-use vs. when-not guidance against siblings like get_job_intent or the other update_* tools, leaving that inference to the agent.

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