Skip to main content
Glama

面灵AI 面试助手

create_resume_from_text

用一段文字新建一份简历(如按用户要求修改后的简历全文),面试与网申可直接选用;不生成文件,原有简历不受影响。返回新简历 ID。(需要用户授权,范围 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": {
      "title": "<title>",
      "content": "<content>"
    },
    "name": "create_resume_from_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes简历标题
contentYes简历全文

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already mark this as a non-readonly, non-destructive, closed-world write. The description adds real context beyond them: it confirms no file is produced and existing resumes are unaffected, it states the return value (new resume ID), and it declares the required authorization scope resumes:write.

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 description is a single dense line with the action front-loaded, followed by clarification of effects, return value, and authorization. Every clause carries information, though the parentheticals make it slightly crowded.

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

Completeness4/5

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

For a two-parameter write tool with no output schema, it covers the essentials: what is created, that no files are generated, that existing resumes are untouched, what is returned, and the auth scope. The only gap is that schema fields are not explicitly mentioned in prose.

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 100% with both title and content fully described in the input schema. The description alludes to the content parameter ('一段文字'), but it adds no format, length, or structuring guidance beyond what the schema already supplies, so the baseline 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 gives a specific verb and resource: creating a new resume from text such as a revised full resume. It implicitly contrasts this with file-based creation with '不生成文件', which sets it apart from upload-style siblings, but it never names an alternative, so it falls just short of a full 5.

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 states a concrete use case: a revised resume full text based on the user's requirements. It also says the result can be selected directly for interviews and online applications, which clarifies downstream use. There is no explicit when-not guidance or named alternative.

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