Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

goat_countries

Retrieve every country GOAT recognizes as a valid country_code, including localized currency, size unit, and whether shipping and returns are supported. Filter by ships_to for shipping destinations.

Instructions

Get GOAT countries. Returns every country GOAT recognizes -- the accepted values for GET /goat/product/{slug}'s country_code parameter -- with the currency and size unit (us, uk, eu) GOAT localizes to for each, plus whether GOAT ships and accepts returns there. Every country is listed, not only the shippable ones, because country_code localizes pricing and is accepted for all of them; filter on ships_to if you want only GOAT's shipping destinations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full disclosure burden, and it does so well: it explains that ALL countries are returned (not only shippable ones) and why — country_code localizes pricing and is accepted everywhere. It omits auth requirements and any rate limits, but the return semantics are unusually well spelled out.

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?

Front-loads what the tool returns before the scoping rationale. Four sentences is slightly longer than strictly necessary, but the extra 'every country, not just shippable ones' clause earns its place by preventing a wrong inference about the result set.

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?

No input schema, no output schema, and no annotations, so the description must describe the return payload itself — and it does, listing currency, size unit, ships_to, and returns. Only the absence of auth/rate-limit context keeps this from being fully complete.

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 tool takes zero parameters, so the baseline is 4. The description does reference a 'ships_to' filter, but that refers to the returned data rather than an input parameter, so no additional input semantics are needed or provided.

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?

States a specific verb and resource ('Get GOAT countries') and elaborates on exactly what the result set contains: every country GOAT recognizes, with currency, size unit, and shipping/returns flags. It also positions the tool as the source of valid values for goat_product's country_code parameter, distinguishing it from the product/search siblings.

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?

Gives clear context: use it to obtain the accepted country_code values for GET /goat/product/{slug}, and filter on ships_to if only shipping destinations matter. It does not enumerate exclusions or name an alternative tool, but for a reference/lookup endpoint the intended use is unambiguous.

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