Skip to main content
Glama
Sign In
warp-agent-mcp

warp-agent-mcp

Official
by warpfreight
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Remote

warp_delete_load_template

Destructive

Delete a saved load template by its ID to remove unused freight planning templates from your account.

Instructions

Delete a saved load template by its id (starts with lt_). Auth required.

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": {
      "load_template_id": "<load_template_id>"
    },
    "name": "warp_delete_load_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
load_template_idYesTemplate id to delete (starts with lt_)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.1

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already provide destructiveHint=true. The description adds the requirement for authentication, which is not in the annotations. It does not mention reversibility or side effects, but for a simple delete, this is adequate.

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 a single sentence with no unnecessary words. It is extremely concise and to the point.

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 one-parameter delete tool, the description covers purpose, parameter format, and auth requirement. No output schema is needed, and it is 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 covers the parameter fully, but the description adds that the id starts with 'lt_', providing extra context 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 (delete), the target (saved load template), and the identifier format (starts with lt_). It distinguishes from sibling tools like warp_save_load_template and warp_load_templates.

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

Usage Guidelines4/5

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

The description mentions 'Auth required,' which is a condition for usage. While not explicitly stating alternatives, the context and sibling list make it clear when to use this tool vs others, but it could be more explicit.

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