Skip to main content
Glama
brentwpeterson

Strety MCP Server

strety_delete_todo

Permanently delete a todo from Strety. This action is irreversible, use it to remove completed or unwanted tasks.

Instructions

Permanently delete a todo from Strety. This cannot be undone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
todoIdYesThe ID of the todo to delete
Behavior4/5

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

With no annotations, the description carries full burden. It clearly states the destructive nature ('permanently delete') and the irreversible effect ('cannot be undone'), which is sufficient for a simple delete operation.

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?

Two efficient sentences: the first explains the action, the second emphasizes irreversibility. No unnecessary words; front-loaded with key information.

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 simple delete-by-ID tool with no output schema and full parameter coverage, the description is complete. It explains the action and the irreversible consequence, which is all the agent needs.

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 (100% coverage) already describes the todoId parameter. The description adds no additional meaning beyond what the schema provides, so baseline score of 3 applies.

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 tool 'permanently delete a todo from Strety', specifying the action and resource. It distinguishes itself from sibling tools (strety_create_todo, strety_update_todo, etc.) as the only delete operation.

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 usage for deleting a todo with an irreversibility warning, but does not provide explicit guidance on when to use it versus alternatives, nor conditions for usage.

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/brentwpeterson/mcp-strety'

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