Skip to main content
Glama

l402_delete_resource

Deletes a specified resource from the configured L402 gateway using its resource identifier.

Instructions

Delete a resource from the configured L402 gateway.

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": {
      "resource_id": "<resource_id>"
    },
    "name": "l402_delete_resource"
  }
}

Input Schema

NameRequiredDescriptionDefault
resource_idYesResource identifier to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing: it does not say whether deletion is permanent, whether it requires L402 payment/authentication, what happens to an already-deleted or unknown resource_id, or what is returned. For a destructive tool with zero annotation coverage this is a substantial gap.

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?

One short sentence, front-loaded with the action and scoped to the gateway, with no filler. It is efficient but borders on under-specification rather than demonstrating good structure.

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?

A destructive single-parameter tool with no annotations and no output schema needs the description to explain irreversibility, auth/payment requirements, and failure modes. None of that is present, so an agent cannot safely predict the consequences of calling it.

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 resource_id parameter, so the schema already explains its meaning and the description adds nothing beyond it. Baseline 3 is appropriate since the schema does the work.

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?

States a specific verb ("Delete") and resource ("a resource") scoped to "the configured L402 gateway," which is unambiguous about intent. It does not, however, differentiate itself from siblings like l402_create_resource or l402_list_resources, so the agent must infer the boundary from the names alone.

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?

There is no statement of when to use this versus listing, inspecting, or creating resources, nor any prerequisite, confirmation, or caution guidance for a destructive operation. The agent is left to infer timing and preconditions from the tool name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.