Skip to main content
Glama

面灵AI 面试助手

delete_resume

Destructive

删除用户的一份简历。简历 ID 取自 list_resumes。删除后不能恢复,执行前向用户说明要删除的内容并取得同意。(需要用户授权,范围 resumes: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": {
      "resumeId": "<resumeId>"
    },
    "name": "delete_resume"
  }
}

Input Schema

NameRequiredDescriptionDefault
resumeIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description is not the sole source of the danger signal. It still adds real context beyond the annotations: deletion is irreversible ('删除后不能恢复'), an explicit user-consent step is required, and the operation needs the resumes:write authorization scope. Response or error behavior is left unstated, which keeps this from a 5.

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?

Four short clauses, front-loaded with the action, then the ID source, then the irreversibility/consent warning, then the auth scope. Every clause carries information an agent needs and none is redundant.

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 one-parameter destructive tool with no output schema, the definition covers what is deleted, where the ID comes from, irreversibility, the consent requirement, and the authorization scope. Safety annotations plus this text leave nothing material missing before invocation.

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% and the schema is a bare string, but the description supplies the one thing the schema cannot: where the resumeId comes from (list_resumes). That is the key semantic an agent needs for this parameter, though nothing is said about ID format or how to handle an invalid or already-deleted ID.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('删除用户的一份简历' – delete one of the user's resumes) with the scope explicitly limited to a single resume. It also names the sibling that supplies the identifier (list_resumes), so the agent can separate this from retrieval tools without opening a schema.

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 a concrete precondition sequence: obtain the resumeId from list_resumes, explain to the user what will be deleted, and get consent before executing. It does not discuss when a resume should not be deleted or what to do if the user declines, but for a single-purpose destructive tool the guidance is clear and actionable.

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