Skip to main content
Glama

Get a free US shipping address (package forwarding sign-up)

get_started
Read-onlyIdempotent

Step-by-step instructions to sign up for a free Global Shopaholics US shipping address and start shopping and shipping. Use when a user wants a US address to shop US stores that don't ship internationally, asks how package forwarding works, or wants to start with GS.

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

Input Schema

NameRequiredDescriptionDefault
countryNoOptional: user's country, to tailor tips.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly=true, idempotent=true, destructive=false, so safety is covered. The description adds the key behavioral fact beyond annotations: this returns instructional content ('step-by-step instructions') rather than account or shipment data, and it discloses the 'free' attribute of the address. It stops short of saying anything about output format or length.

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?

Two sentences, front-loaded with what the tool produces and followed immediately by when to use it. Minor redundancy between 'start shopping and shipping' and 'wants to start with GS', and the opening is a noun phrase rather than a verb phrase, but nothing is wasteful.

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 single-optional-parameter, read-only guidance tool with no output schema, the description supplies purpose, trigger conditions, and the nature of the return (instructions). It could mention that it returns informational steps rather than performing the sign-up, but the essentials are present.

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 the single optional 'country' parameter is already documented as tailoring tips, so the schema carries the parameter semantics. The description adds no additional meaning about how country affects the instructions; baseline 3 is appropriate.

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 names a specific resource (a free Global Shopaholics US shipping address) and a specific deliverable (step-by-step sign-up instructions). It is clearly distinguishable from rate/quote/tracking siblings by being a sign-up/guidance tool rather than a data tool.

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 gives explicit trigger conditions: user wants a US address for stores that don't ship internationally, asks how package forwarding works, or wants to start with GS. It does not name any exclusion or point to a sibling alternative (e.g. fees or rates), which keeps it below a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.