Skip to main content
Glama

prepare_application_batch

Prepares tailored resumes and application emails for multiple selected jobs after you review each proposal, requiring an accepted proposalId per job or an explicit keepOriginal choice. It only prepares items and reports per-job blockers.

Instructions

用户核对修改后,一次准备所选岗位的专属简历和邮件。每项要提供已查看的 proposalId 与接受项,或用户明确选择 keepOriginal。只准备,不批准或发送;逐项报告阻塞原因。

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": {
      "goalId": "<goalId>",
      "choices": "<choices>"
    },
    "name": "prepare_application_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalIdYes
choicesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, closed-world write; the description adds the key behavioral facts beyond that: no approval or sending occurs, each item is reported individually, and blocking reasons are surfaced per item. It stops short of describing what a blocked vs prepared result looks like, but with annotations covering the safety profile this is solid added value.

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?

Three short sentences with the precondition front-loaded, then the per-item requirement, then the scope limit. Dense and mostly waste-free, though the '只准备,不批准或发送' clause is packed into the same sentence as the per-item blocking report, slightly muddying the structure.

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 two-parameter mutation tool with no output schema, it covers the precondition, the per-item input contract, the non-approving scope, and the per-item error reporting. What is missing is a description of what a successful prepared result contains, which is a modest gap given the absence of an output schema.

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 0%, so the description must carry the burden, and it does explain the crucial nested semantics of choices: each entry needs a previously viewed proposalId plus accepted items, or an explicit keepOriginal flag. It leaves goalId and the 1–20 item bound to the schema, which is a minor gap rather than a blocking one.

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?

Names a specific verb (准备 / prepare) and concrete artifacts (专属简历和邮件), plus the batch scope implied by '一次…所选岗位' which contrasts with the singular prepare_application. It does not name any sibling outright, so the differentiation is inferred rather than stated.

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?

Gives an explicit precondition ('用户核对修改后') and a per-item gate ('已查看的 proposalId 与接受项,或用户明确选择 keepOriginal'). It also bounds scope by saying it does not approve or send, which points the agent to the execution tool without naming it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.