Skip to main content
Glama

面灵AI 面试助手

update_job_apply_profile

修改用户网申档案中的标准字段:只改传入的键,其余不动;值传空字符串或空数组即清空该字段。键名见 get_job_apply_profile。回包为读回的值。(需要用户授权,范围 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_apply_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
patchYes要修改的字段:键为标准字段名,值为字符串或字符串数组(多段经历按条目传数组)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already mark this as a non-read-only, non-destructive, closed-world write. The description adds important behavior beyond that: it is a partial update with a clear rule, it states the required authorization scope (job_applications:write), and it describes the response as the values read back after the update. It does not state whether clearing a field through an empty value is reversible or how it differs in effect from the delete sibling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is compact and front-loaded. The patch rule comes first, then clearing, then key reference, then response and auth. Every clause contributes a distinct fact.

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 partial-update tool with full schema coverage and no output schema, the description covers mutation semantics, clearing, key lookup, authorization scope, and return behavior. The one remaining gap is the choice between clearing through this tool and the dedicated field-delete sibling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the field enumeration is already documented. The description nevertheless adds meaning the schema lacks: it explains that patch keys are standard field names looked up via get_job_apply_profile, that the empty-string and empty-array values clear a field, and that only the supplied keys are touched. This is useful semantics beyond the enum list.

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: it modifies standard fields in the user's job-application profile, and it points to get_job_apply_profile for the key names. That distinguishes it from the read tool and from the field-deletion sibling. However, it never says how it differs from delete_job_apply_profile_field, even though it can clear a field.

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?

The patch semantics are clear: only the keys you pass are changed, and the other keys are left alone. It also includes an explicit clearing rule, where an empty string or empty array clears the field. It does not state when not to use it, or whether clearing through this tool is preferable to delete_job_apply_profile_field.

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