Skip to main content
Glama

面灵AI 面试助手

delete_learned_profile_answer

Destructive

删除一条随投递学到的长尾问答,之后不再自动填入其他公司的申请表。删除后不能恢复,执行前向用户说明要删除的内容并取得同意。(需要用户授权,范围 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": {
      "normalized": "<normalized>"
    },
    "name": "delete_learned_profile_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
normalizedYes长尾问答的归一化键,从 get_job_apply_profile 原样取得

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description goes further by disclosing irreversibility ('删除后不能恢复'), the downstream effect on auto-fill for other companies' forms, the mandatory user-consent step, and the required authorization scope (job_applications:write). Those are exactly the behavioral facts an agent cannot read off the structured fields.

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?

Every clause carries distinct information – action, effect, irreversibility, consent requirement, and auth scope – with the destructive consequence front-loaded immediately after the action. There is no redundant restatement of the name or title.

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 annotations and no output schema, the description covers everything needed: what is destroyed, that it cannot be undone, that consent must be obtained, and what authorization is required. No meaningful gap remains for an agent deciding whether and how to call it.

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?

With a single parameter at 100% schema description coverage, the schema already explains that 'normalized' is the normalized key obtained as-is from get_job_apply_profile. The prose adds no further meaning about the parameter's format or failure modes, so the baseline 3 applies.

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 specific verb and resource ('删除一条随投递学到的长尾问答') and even names the functional consequence ('之后不再自动填入其他公司的申请表'), so an agent knows exactly what is removed and why. It does not explicitly distinguish itself from the closely named sibling edit_learned_profile_answer, leaving that differentiation to the tool names alone.

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?

It gives clear procedural preconditions: explain to the user what will be deleted and obtain consent before executing, and it implies the key should come from get_job_apply_profile. It stops short of stating when to prefer deletion over editing the learned answer, so there is no explicit exclusion or alternative routing.

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