Skip to main content
Glama

删除机构标签

classin_delete_school_label
DestructiveIdempotent

Delete a school label permanently by providing its label ID. This action is irreversible and cannot be undone.

Instructions

删除机构标签。删除后不可恢复。

参数:

  • labelId: 要删除的标签ID

返回:

  • 成功返回操作结果

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelIdYes要删除的标签ID
response_formatNo输出格式: 'markdown' 人类可读格式 或 'json' 机器可读格式markdown
Behavior4/5

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

The description states that deletion cannot be recovered, which adds meaningful context beyond the destructiveHint annotation. It also mentions a return result on success, though it does not detail error handling or side effects. This does not contradict any annotations.

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?

The description is short and well-structured with a clear purpose statement followed by parameters and return sections. It is front-loaded, though it duplicates parameter information already in the schema, making it slightly redundant but still concise.

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 simple delete operation with one required parameter, the description provides the core purpose and the key warning of irreversibility. It lacks explicit error handling details and does not describe the exact return format, but given the simplicity and available annotations, it is reasonably complete.

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?

The description lists labelId with the same wording as the schema, adding no new meaning. Schema coverage is 100%, so the baseline is 3; the description does not compensate or add nuance for either parameter, including response_format.

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 explicitly states '删除机构标签' (delete institution label), using a specific verb and resource, and distinguishes it from sibling tools like add_school_label or update_school_label by clearly indicating deletion. The irreversibility note further clarifies the intent.

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?

The description implies when to use the tool (when deleting a label) but does not explicitly contrast it with alternatives such as add or update school label. No exclusions or prerequisites are mentioned, leaving usage guidance mostly implicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yuanlang12/classin-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server