Skip to main content
Glama
Launch-On-Basis

Basis MCP Server

Official

delete_reef_comment

Remove a specific comment from the reef by providing its unique comment ID.

Instructions

Delete your reef comment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
comment_idYes
Behavior2/5

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

No annotations exist, so the description must carry behavioral transparency. 'Delete' implies destruction, but the description does not state irreversibility, required ownership, or any side effects (e.g., removing associated votes). The hint 'your' is not enough.

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 a single, short sentence that is clear and to the point. However, it omits critical details that could be included without verbosity, such as ownership and permanence.

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

Completeness2/5

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

Without output schema or annotations, the description should cover fundamental aspects of a delete operation. It fails to mention that deletion is permanent, requires ownership, or what happens to associated data like votes or replies. This is insufficient for an AI agent to reliably invoke the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The only parameter, 'comment_id', has no description in the schema (0% coverage) and the tool description provides no explanation of its meaning or source. The agent must infer its purpose and format without guidance.

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 'Delete your reef comment' clearly identifies the action (delete) and resource (reef comment). It distinguishes from siblings like 'delete_reef_post' and 'edit_reef_comment'. The possessive 'your' implies ownership, adding a bit of specificity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives such as 'delete_project_comment' or 'edit_reef_comment'. There are no prerequisites, exclusions, or context about ownership or permissions.

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/Launch-On-Basis/MCP-TS'

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