Skip to main content
Glama

面灵AI 面试助手

unshare_question_prediction

取消一条押题的公开分享,之前发出的分享链接随即无法打开。记录 ID 取自 list_question_predictions。(需要用户授权,范围 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": "unshare_question_prediction"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes押题记录 ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false), the description discloses the real consequence that previously issued share links become inaccessible, and it states the required authorization scope (interviews:write). It does not describe failure modes (e.g., what happens if the record was never shared), keeping it below a 5.

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?

Three short sentences, front-loaded with the action and its effect, followed by the ID source and the auth requirement. No redundant or filler wording.

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

Completeness5/5

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

For a single-parameter mutation with annotations and no output schema, the description covers the action, its side effect on existing links, where to get the ID, and the authorization scope. Nothing an agent needs to invoke it correctly is missing.

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% and there is only one parameter, so the schema already defines 'id'. The description adds provenance value by saying the ID should be obtained from list_question_predictions, which is meaning beyond the schema's '押题记录 ID' 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 states a specific verb and resource ('取消一条押题的公开分享' – cancel the public sharing of a question prediction) and immediately names the observable effect (existing share links stop working). This clearly distinguishes it from the sibling share_question_prediction, which does the opposite.

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 tells the agent where the required ID comes from ('记录 ID 取自 list_question_predictions'), which is a concrete usage prerequisite. It does not explicitly state when not to use it or name the inverse share tool as an alternative, so it falls short of full when/when-not guidance.

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