Skip to main content
Glama
baskcart

W3Ship MCP Server

by baskcart

ship_address

Retrieve a physical shipping address by verifying a cryptographic signature linked to a public key identity, enabling anonymous address lookup for order fulfillment.

Instructions

Securely retrieve a physical address using a public key and a timed cryptographic signature.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
publicKeyYesThe hex-encoded public key to lookup.
signatureYesThe hex-encoded signature of the timestamp.
timestampYesThe current Unix timestamp in milliseconds.

Implementation Reference

  • The tool 'ship_address' forwards an identity lookup request to the centralized W3Ship API for verification and address retrieval.
    case "ship_address": {
        // Forward the identity lookup to the centralized W3Ship API.
        // Signature verification and DB lookup happen server-side.
        const { publicKey, signature, timestamp } = args as any;
    
        if (!publicKey || !signature || !timestamp) {
            return { content: [{ type: 'text', text: 'Error: publicKey, signature, and timestamp are all required.' }], isError: true };
        }
    
        const identityRes = await fetch(`${W3SHIP_API}/api/identity`, {
            method: 'POST',
            headers: { 'Content-Type': 'application/json' },
            body: JSON.stringify({ publicKey, signature, timestamp }),
        });
    
        const identityData = await identityRes.json();
    
        if (!identityRes.ok) {
            return {
                content: [{ type: 'text', text: `Error: ${identityData.error || 'Identity lookup failed'}${identityData.details ? ' — ' + identityData.details : ''}` }],
                isError: true,
            };
        }
    
        return {
            content: [{ type: 'text', text: JSON.stringify(identityData, null, 2) }],
        };
    }
  • src/index.ts:51-63 (registration)
    Tool registration for 'ship_address' in the listTools handler.
    {
        name: "ship_address",
        description: "Securely retrieve a physical address using a public key and a timed cryptographic signature.",
        inputSchema: {
            type: "object",
            properties: {
                publicKey: { type: "string", description: "The hex-encoded public key to lookup." },
                signature: { type: "string", description: "The hex-encoded signature of the timestamp." },
                timestamp: { type: "number", description: "The current Unix timestamp in milliseconds." },
            },
            required: ["publicKey", "signature", "timestamp"],
        },
    },
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the security model ('securely', 'timed cryptographic signature') implying replay protection and authentication requirements, but omits failure modes, rate limits, or return value structure.

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, dense sentence of 11 words. Every word earns its place: action ('retrieve'), resource ('physical address'), and security mechanism ('public key', 'timed cryptographic signature') are all front-loaded with zero redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for invoking the tool given the well-documented schema, but incomplete regarding what the tool returns (no output schema exists) and error conditions (e.g., invalid signature behavior). Given the 'secure' nature, more behavioral context would strengthen this.

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%, establishing a baseline of 3. The description adds minimal semantic value beyond the schema—'timed' reinforces the timestamp-signature relationship already documented in the schema, but doesn't explain parameter formats or validation rules beyond 'hex-encoded'.

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 action ('retrieve') and resource ('physical address') clearly. The cryptographic mechanism distinguishes it implicitly from sibling getters like get_identity, though it doesn't explicitly differentiate from them.

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?

Provides no guidance on when to use this tool versus alternatives (e.g., get_identity) or prerequisites for the cryptographic signature. The 'securely' qualifier hints at sensitive use cases but lacks explicit direction.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/baskcart/w3ship-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server