Skip to main content
Glama
Sign In
mcploy

mcploy

by ogarciabrena
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete modifier

loyverse_delete_modifier

Delete a modifier by ID in Loyverse. This operation is destructive and cannot be undone.

Instructions

Delete a modifier by id (DELETE /modifiers/{id}). This is destructive and cannot be undone.

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": "loyverse_delete_modifier"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe modifier id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries full burden. It explicitly notes the action is 'destructive and cannot be undone,' which is critical behavioral transparency for a delete operation. It does not mention potential side effects or error conditions, but the simplicity of the tool limits the need.

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 with two sentences, no fluff. It front-loads the action and resource, then adds the critical destructive note. Every word is necessary.

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?

Given no output schema and low complexity (single parameter), the description adequately covers the tool's purpose and destructiveness. It does not specify the return value or confirm deletion, but for a simple delete, this is sufficient.

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 schema covers 100% of parameters with a description of 'id' as 'The modifier id.' The description adds 'by id,' which confirms the parameter's role. Since schema coverage is high, the description adds minimal extra meaning, meeting the baseline of 3.

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 modifier'), and includes the HTTP endpoint for reference. This distinguishes it from other delete tools targeting different resources (e.g., category, customer).

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 via the verb 'delete' and the endpoint, but does not explicitly state when to use this tool versus alternatives like updating or listing modifiers. There is no guidance on prerequisites or when not to use it.

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