Skip to main content
Glama

面灵AI 面试助手

rename_interview

修改一场面试记录的标题(实时面试与模拟面试均可)。(需要用户授权,范围 interviews: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": {
      "interviewId": "<interviewId>",
      "title": "<title>"
    },
    "name": "rename_interview"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
interviewIdYes面试 ID,取自 list_interviews

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the mutation-versus-safe-read question is settled by structured data. The description adds genuine value beyond that by disclosing the required authorization scope (interviews:write), but it says nothing about what happens on an invalid interviewId or whether the previous title is recoverable.

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?

Two short sentences with the action and its scope front-loaded, and the auth requirement tucked into a parenthetical rather than padding the opening. Nothing is wasted, though the trailing parenthetical could be trimmed to a single clause.

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, non-destructive mutation with no output schema, the definition covers the essentials: what changes, which interview types, and what credential is needed. The remaining gap, error behavior for an unknown interviewId, is minor at this complexity level.

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 50%: interviewId carries its own description ('取自 list_interviews') while title relies on minLength/maxLength constraints only. The description merely restates that title is the field being changed, adding no format or sourcing detail the schema does not already provide, so the baseline 3 is appropriate.

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 (modify the title of an interview record) and immediately bounds scope by noting it applies to both live and mock interviews. That is clear enough to distinguish it from the sibling tools, none of which rename records, though it does not explicitly contrast itself with any of them.

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 states the applicable contexts (live and mock interviews both), which is useful inclusion guidance, but gives no when-not conditions, no prerequisites beyond the auth scope, and no routing toward alternatives such as delete_interview or create_interview_target.

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