Skip to main content
Glama

prepare_application

Freezes job-specific application attachments and email body, returning an existing record when identical content already exists to prevent duplicate application records.

Instructions

冻结岗位版附件与邮件正文。相同内容返回已有记录,不重复创建。

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": {
      "jobId": "<jobId>",
      "resumeId": "<resumeId>",
      "recipient": "<recipient>",
      "subject": "<subject>",
      "body": "<body>"
    },
    "name": "prepare_application"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
jobIdYes
subjectYes
resumeIdYes
recipientYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already disclose that this is a non-destructive, non-open-world write. The description adds real value beyond that by disclosing deduplication semantics: identical content returns the existing record rather than creating a duplicate. However, it does not explain what 'freeze' concretely produces, whether it is persisted, or what state a subsequent execute_application depends on.

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?

Two compact sentences with no filler, and the idempotency guarantee is front-loaded after the core action. Nothing is wasted, though the brevity is close to under-specification rather than being tight.

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

Completeness2/5

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

For a five-required-parameter write tool with no output schema and zero parameter documentation, the description leaves too much unexplained: what record is created, whether it is a draft, and how it relates to preview_application or execute_application. The idempotency note is the only behavioral detail an agent could not infer.

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

Parameters1/5

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

Schema description coverage is 0% across five required parameters, and the description mentions none of them. There is no explanation of jobId vs. resumeId, what attachments are implied, or what format recipient/subject/body take, so the description fails to compensate for the coverage gap.

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 states a concrete action and resource: freezing the job-posting version's attachments and email body. 'Freeze' is somewhat opaque (snapshot? lock? persist?) but the overall intent to prepare a fixed application payload is clear. It does not distinguish itself from siblings like prepare_application_batch, preview_application, or execute_application.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this versus preview_application, prepare_application_batch, revise_application, or execute_application. The only conditional stated is idempotency ('same content returns existing record'), which describes outcome behavior rather than selection guidance.

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