Skip to main content
Glama
okareo-ai

Okareo MCP Server

Official
by okareo-ai
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Delete Scenario

delete_scenario
Destructive

Permanently delete a scenario and its test data by providing the scenario ID and name. Confirm via preview to avoid accidental loss.

Instructions

Permanently delete a scenario and all related test data.

    Both scenario_id and name are required. Use preview_delete_scenario first
    to see what will be deleted before confirming.

    Args:
        scenario_id: The ID of the scenario to delete (from preview_delete_scenario).
        name: The name of the scenario to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
scenario_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

Annotations already mark destructiveHint=true, and the description enhances this by stating 'permanently delete' and 'all related test data', clarifying the scope and irreversibility. It also adds the safety practice of previewing, going beyond the structured annotations.

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 short, front-loaded with the core action, and presents usage guidance and parameter details efficiently without redundancy.

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 destructive tool with an output schema, the description sufficiently covers prerequisites, the destructive scope, and the recommended preview step, making it complete for its complexity.

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

Parameters4/5

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

The schema provides basic names/types, and the description adds context for scenario_id (from preview_delete_scenario) and reiterates that both are required. With 0% schema coverage, it partially compensates but could offer more detail on how to obtain or validate the name.

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 uses the specific verb 'delete' with the resource 'scenario' and adds scope ('all related test data'), clearly distinguishing it from sibling tools like preview_delete_scenario and other delete_* tools.

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

Usage Guidelines5/5

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

Explicitly instructs to use preview_delete_scenario first before confirming deletion, providing direct guidance on proper tool sequencing and when to invoke this tool.

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/okareo-ai/okareo-mcp'

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