Skip to main content
Glama
Sign In
Lenx MCP Server

Lenx MCP Server

by ThinkCol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

lenx_delete_task

Delete a monitoring task by providing its task ID. Only the task owner is allowed to perform this action.

Instructions

Delete a monitoring task. Only the task owner can perform this operation.

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": {
      "task_id": "<task_id>"
    },
    "name": "lenx_delete_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYesTask ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of disclosure. It states the destructive nature (delete) and the ownership requirement. However, it does not detail what happens on success or failure (e.g., whether deletion is permanent or reversible), leaving some behavioral gaps.

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 extremely concise: two clauses in one sentence. Every word adds value, stating the action, the resource, and a key constraint. There is no unnecessary 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 simple delete operation with a single required parameter, the description adequately covers the core functionality and an important precondition. It does not explain error handling or return values, but these are often implicit for delete tools. Given the lack of output schema, the completeness is acceptable.

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 input schema has 100% description coverage, and the parameter description 'Task ID to delete' is clear. The tool description adds the context that the task is a 'monitoring task', but does not provide additional semantic meaning beyond the schema, so baseline 3 is appropriate.

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 clearly states the action ('Delete') and the resource ('a monitoring task'), making the purpose unambiguous. It also specifies the ownership constraint, which adds to clarity. This distinguishes it from siblings like lenx_create_task or lenx_update_task.

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?

The description provides an explicit prerequisite: only the task owner can perform the operation. This helps the agent understand when the tool is applicable. However, it does not explicitly mention when not to use it or suggest alternatives, though for a delete operation, this is rarely needed.

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