warp-agent-mcp

Official

by warpfreight

Overview Schema Source Related Servers Discussions(1)Admin

TypeScript

Remote

warp_get_invoice

Read-only

Retrieve a delivered shipment's invoice, including line items, taxes, and payment status using the order ID.

Instructions

Retrieve the invoice for a delivered shipment (line items, taxes, payment status). 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": {
      "order_id": "<order_id>"
    },
    "name": "warp_get_invoice"
  }
}

Input Schema

Name	Required	Description	Default
`order_id`	Yes	Order ID (typically the same as shipment_id)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.10.1May 28, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already indicate readOnlyHint=true, so the description adds 'Auth required' and the precondition of a delivered shipment. However, it does not disclose error behavior, rate limits, or response format beyond what annotations provide.

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 of 15 words, front-loaded with the purpose and key constraints. No redundant 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 tool with one required parameter and good annotations, the description covers purpose, precondition (delivered shipment), and auth requirement. Lacks explicit return format, but this is acceptable given no output schema.

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 coverage is 100% and already describes the order_id parameter sufficiently. Description adds 'Auth required' but no further parameter-specific details, so value beyond schema is minimal.

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?

Description clearly states the tool retrieves an invoice for a delivered shipment, specifying the verb 'retrieve' and resource 'invoice for a delivered shipment'. It distinguishes from siblings like warp_payment_status and warp_get_documents by focusing on invoice retrieval.

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 use only for delivered shipments but does not explicitly state when not to use or mention alternatives. No guidance is provided on prerequisites or error scenarios.

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