Skip to main content
Glama
Sign In
Picsha AI MCP Server

Picsha AI MCP Server

Official
by picsha-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

delete_asset

Permanently remove a digital asset from the database, search indexes, and physical storage by providing its unique ID.

Instructions

Permanently delete an asset from the database, search indexes, and physical storage.

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": {
      "id": "<id>"
    },
    "name": "delete_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe unique ID of the asset to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.12

TDQS

A3.6/5.0
Behavior3/5

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

Discloses permanent deletion affecting multiple layers, but no annotations provided. Lacks details on authorization, irreversibility confirmation, or side effects.

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?

Single sentence, no unnecessary words, front-loaded with critical 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 deletion with one parameter, the description provides essential behavioral context. Could be improved with usage caveats but is adequate.

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?

Schema description coverage is 100% for the single parameter 'id'. The tool description does not add extra meaning beyond the schema.

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 (permanently delete), the resource (asset), and the scope (database, search indexes, physical storage). It distinguishes from siblings like 'get_asset' or 'update_asset'.

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 on when to use versus alternatives like 'moderate_asset' or 'update_asset'. Does not specify prerequisites or conditions for deletion.

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