Skip to main content
Glama
Sign In
传承·交大 MCP

传承·交大 MCP

by Flagwill
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

share_report_material

Destructive

Flag a shared material by submitting its ID and a valid reason code; set confirm to true to complete the report.

Instructions

举报资料；reason 使用举报原因接口返回的 code。confirm=true 执行。

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": {
      "material_id": "<material_id>",
      "reason": "<reason>"
    },
    "name": "share_report_material"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYes
confirmNo确认用户已授权此次操作后设为 true
descriptionNo
material_idYes平台对象 ID，正整数

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true. The description adds the important execution gate, 'confirm=true 执行', implying default confirm=false does not execute, but it does not describe the actual consequence of reporting or what confirm=false does beyond implication.

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?

The description is two short clauses, front-loads the action, and contains no filler. Every phrase carries operational meaning.

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

Completeness3/5

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

It covers the core action, the reason-code prerequisite, and confirm gating, and an output schema exists for return values. However, for a destructive action it does not explain side effects, whether confirm=false is a dry run, or the purpose of the description parameter.

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%, with confirm and material_id documented in the schema. The description adds essential meaning for the required reason parameter by tying it to codes returned by the report reasons interface, but it leaves the description parameter unexplained and does not clarify the reason code format.

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, '举报资料' (report material), which clearly separates it from the sibling share_report_comment. It does not explicitly mention sibling alternatives, but the resource distinction is unambiguous.

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 concrete procedural context: fetch the reason code from the material report reasons interface, and set confirm=true to execute. This is clear guidance on prerequisites and execution gating, though it does not state explicit when-not-to-use conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools