Skip to main content
Glama

面灵AI 面试助手

share_question_prediction

为一条已完成(done)的押题生成公开分享链接。访客打开只能看到总述与前 3 题的题干和考察点,看不到作答思路与简历素材。记录 ID 取自 list_question_predictions;可用 unshare_question_prediction 取消。(需要用户授权,范围 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": {
      "id": "<id>"
    },
    "name": "share_question_prediction"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes押题记录 ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the exact exposure surface: visitors see only the overview plus the stems and assessment points of the first three questions, and never the answer approaches or resume materials. It also discloses an authorization requirement and scope (interviews:write), which the annotations do not convey.

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?

Four tight clauses with no filler, front-loaded with the action and precondition, followed by data-exposure scope, parameter provenance, the inverse tool, and the auth requirement. Every sentence carries distinct information.

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 one-parameter, non-destructive mutation, the definition covers precondition, privacy scope, parameter source, inverse operation, and authorization. The only small gap is that it never states what the call returns (presumably the share URL), which matters slightly since no output schema exists.

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 coverage is 100% for the single 'id' parameter, so the baseline is 3, but the description adds genuine meaning by stating that the ID originates from list_question_predictions. That provenance is the main practical pitfall for this parameter and is not in the schema.

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?

Names a specific verb and resource (generate a public share link for a completed question-prediction record) plus the precondition that the record must already be 'done'. This clearly separates it from siblings such as unshare_question_prediction and delete_question_prediction without the reader needing to open any schema.

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?

Gives real routing guidance: the ID must come from list_question_predictions, the record must be in the 'done' state, and unshare_question_prediction is named as the inverse operation. It stops short of stating explicit exclusion cases (for example, what happens or what to do when the record is not yet done), so it is strong but not exhaustive.

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