Skip to main content
Glama

面灵AI 面试助手

draft_boss_hr_replies

Read-only

按用户的基础简历,为 Boss 直聘上最多两位 HR 的最近消息各拟一条回复草稿(只生成文字,不发送)。HR 消息由用户提供。(需要用户授权,范围 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": {
      "conversations": "<conversations>"
    },
    "name": "draft_boss_hr_replies"
  }
}

Input Schema

NameRequiredDescriptionDefault
conversationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with '不发送'. Beyond that it discloses a real operational requirement the annotations do not: user authorization with scope job_applications:read. It still says nothing about draft length, tone, or language, which would matter for an output-less tool.

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?

The action, the basis (base resume), the scope limit, and the no-send constraint are all front-loaded in one sentence, with authorization in a trailing parenthetical. Nothing is padding, though the two-HR cap duplicates the schema and could be dropped.

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

Completeness5/5

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

For a single-parameter, read-only tool with no output schema, the definition covers what it does, what it reads, what it refuses to do, and what authorization it needs. That is sufficient for an agent to call it correctly without further inference.

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 coverage is reported at 0%, so the description must compensate, and it does partially: it clarifies that HR messages come from the user and that only the most recent exchanges per HR matter. However, it never explains the conversation object's structure — the from/to distinction, the chronological ordering of messages, or the per-field limits — leaving the caller to read the schema.

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 ('拟一条回复草稿' for HR messages on Boss 直聘) and constrains scope to at most two HRs' most recent messages. The parenthetical '只生成文字,不发送' cleanly separates it from any send-message capability. It does not explicitly contrast itself with a named sibling, which keeps it below a 5.

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 context of use — drafting replies grounded in the user's base resume, with HR messages supplied by the user — and bounds the operation as text-generation only. There is no explicit when-not-to-use guidance or named alternative, and the 'two HRs' limit merely restates the schema's maxItems of 2.

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