Skip to main content
Glama
Sign In

warp-agent-mcp

by io.github.warpfreight
OverviewDiscussionsAdmin

International Settings

international_settings
Read-only

Whether international (Air / Ocean) shipping is enabled on the user's Warp account, which door services it offers, and the rules for a destination or origin country (postal code required or not, how locations are given). Pass country to get that country's rules; omit it for the account settings and the list of blocked countries. Requires a signed-in Warp account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "international_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNoISO alpha-2 code of the country to look up

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds meaningful context: it requires a signed-in Warp account and changes result mode based on the optional country parameter. It does not disclose error handling or rate limits, but the safety profile is already covered by annotations.

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?

The description is three efficient sentences with no filler, and it front-loads the purpose, parameter branching, and auth prerequisite. The first sentence is slightly dense but still readable and useful.

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?

With no output schema and only one optional parameter, the description needs to define the two usage modes and prerequisites. It does so adequately, though it gives only categories of returned data rather than their structure.

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 fully documents country as an ISO alpha-2 code. The description adds conditional semantics not obvious from the schema: providing country returns that country's rules, while omitting it returns account settings and the blocked-country list.

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?

The description clearly states that this returns international shipping settings: Air/Ocean enablement, door services, country rules, account settings, and blocked countries. It is distinguishable from quote/book/customs siblings by being a settings lookup, though it does not name an alternative explicitly.

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?

It explicitly says to pass country to get that country's rules and omit it for account settings and blocked countries, and it states the signed-in account prerequisite. It lacks explicit guidance on when to use international_quote, international_book, or international_customs instead.

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

All warp-agent-mcp toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources