Skip to main content
Glama

面灵AI 面试助手

edit_learned_profile_answer

修改一条随投递学到的长尾问答的值,之后投其他公司遇到同一题时按新值填写。回包为读回的值。(需要用户授权,范围 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>",
      "value": "<value>"
    },
    "name": "edit_learned_profile_answer"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The annotations only declare that this is not destructive and not read-only. Beyond that, the description usefully discloses auth requirements (user authorization plus the job_applications:write scope) and that the response is the value read back after the write, which is meaningful extra context. It does not mention rate limits, reversibility, or what happens to the record if the value is cleared, though.

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?

A compact three-part description: effect, consequence, then response/auth notes. It is front-loaded and it wastes no words, though the parenthetical auth/scope note could be trimmed.

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

Completeness3/5

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

For a simple two-parameter mutation with no output schema, it covers the return value (read-back value) and auth scope. It still leaves the `value` parameter's constraints and the concurrency or overwrite behavior unstated, which leaves a modest gap.

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

Parameters2/5

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

Only `normalized` is described in the schema (obtained verbatim from get_job_apply_profile), which is 50% coverage. The description clarifies that `value` is the new answer used in future form fills, but it adds no format, length, or validation information for that parameter, so the undocumented half of the parameter set is only partially compensated.

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 (edit) plus resource (a long-tail Q&A learned during job applications) and states the downstream effect: future applications reuse the new value. It is clearly distinct from delete_learned_profile_answer, though it does not explicitly name a sibling or contrasting tool.

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?

The mention that future applications will fill in the new value for the same question implies when to use this tool rather than other profile tools. However, there is no explicit when-not-to-use guidance and no named alternative, such as update_job_apply_profile for non-learned fields, leaving the agent to infer the boundary.

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