Skip to main content
Glama

面灵AI 面试助手

submit_interview_experience

以用户名义提交一篇面经(公司、岗位、轮次、面试月份、正文 10–8000 字)。提交后进入人工审核,审核通过才进入题库;审核状态用 list_my_interview_experiences 查看。(需要用户授权,范围 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": {
      "company": "<company>",
      "position": "<position>",
      "content": "<content>"
    },
    "name": "submit_interview_experience"
  }
}

Input Schema

NameRequiredDescriptionDefault
roundNo
periodNo
companyYes
contentYes
positionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare the safety profile (not read-only, not destructive, closed-world); the description adds genuinely new behavior: the submission is not immediately live, it goes through human review with an approval gate, and the call requires an auth scope of interviews:write. It stops short of covering duplicate handling or whether a submitted entry can be edited or withdrawn.

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 single front-loaded sentence with the essential payload and lifecycle facts, followed by a short parenthetical for the auth scope. The nested parentheses make it dense, but every clause carries information the agent needs.

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 write tool with no output schema and no annotations describing auth or lifecycle, the description covers the review pipeline, the approval gate, the status-check path, and the permission scope — enough to call it correctly and set user expectations. Only the return value shape and post-submission edit/withdraw behavior are left open.

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 description coverage is 0%, so the description must carry the semantics, and it does: it maps all five parameters to meanings (company, position, round, interview month, body) and states the body length constraint of 10–8000 characters. 'period' is glossed as 面试月份, which adds meaning beyond the regex pattern. It does not explain the expected vocabulary for 'round' (free string, max 20) or whether 'month' should be the interview date versus submission date beyond the label.

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?

The description names a specific verb+resource ('以用户名义提交一篇面经') and enumerates the payload dimensions (company, position, round, month, body). It also routes the agent to the sibling that handles follow-up status, so the tool is distinguishable from list_my_interview_experiences at a glance.

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 a clear usage context: submit on the user's behalf, then the record enters manual review and only appears in the question bank after approval, with status checked via list_my_interview_experiences. What is missing is explicit guidance on when to prefer this over the adjacent generate_interview_experience tool, so the agent must 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