Skip to main content
Glama
musaceylan

PriceAtlas MCP Server

by musaceylan

list_countries

Retrieve all 27 supported countries with their default currencies and regions for global food price tracking and comparison.

Instructions

List all 27 supported countries with their default currencies and regions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The definition and implementation of the 'list_countries' tool.
    server.tool(
      'list_countries',
      'List all 27 supported countries with their default currencies and regions.',
      {},
      async () => {
        try {
          const countries = await api('/api/countries');
          return text(countries);
        } catch (e) {
          return errorResult(`List countries failed: ${(e as Error).message}`);
        }
      },
    );
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses the limited scope ('27 supported') and return fields ('currencies and regions'), but lacks safety indicators (read-only/destructive), rate limits, or caching behavior.

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 efficient sentence contains specific numeric constraints and return structure without redundancy. Every clause earns its place.

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 zero-parameter tool without output schema, the description adequately compensates by specifying the return payload structure (countries with currencies and regions). Only minor gaps remain regarding response format or pagination.

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?

Zero parameters present, which establishes a baseline of 4 per the scoring rubric. No parameter description is needed in the text since the empty schema is self-documenting.

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?

Clear specific verb ('List') and resource ('countries') with scope details ('27 supported', 'default currencies and regions'). However, it does not explicitly differentiate from siblings like list_stores or price-related tools that might require country codes.

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?

No explicit guidance on when to invoke this versus sibling tools, nor does it mention that the output can be used as input for other tools (e.g., get_prices). Users must infer usage from the tool name alone.

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/musaceylan/priceatlas-mcp'

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