Skip to main content
Glama

List countries

crunch_list_countries
Read-only

Retrieve countries Crunch supports, including country codes for addresses and supplier records and EU membership status, to validate and populate country data.

Instructions

List the countries Crunch knows, with the country codes to use in addresses and supplier records, and whether each is an EU member.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of items
fieldsNoKeep only these fields (dot paths, such as supplier.companyName)
searchNoCase-insensitive substring match on any value

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

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 openWorldHint=false, so safety is covered; the description still earns credit for disclosing the shape of the payload (codes plus an EU flag), which is behavior beyond the annotations. It omits how the limit/fields/search controls affect results, keeping it short of a 5.

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?

A single front-loaded sentence that identifies the resource first and then its payload, with no filler or redundancy.

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 flat reference-list tool with annotations covering read-only safety and a fully described schema, the description supplies enough: what the list contains and the two useful attributes per entry. Return-value formatting is not explained, but no output schema exists and the content is summarized adequately.

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 description coverage is 100%, so limit, fields, and search are already fully documented in the input schema. The description adds no further meaning about these parameters, which is the expected baseline when the schema does the work.

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 gives a specific verb and resource ("List the countries Crunch knows") and goes further to say what each record carries: country codes for use in addresses and supplier records, plus an EU-membership flag. That content profile makes it unmistakable against siblings like crunch_list_vat_types or crunch_list_payment_methods.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: mentioning that the codes are what you use in addresses and supplier records hints at why an agent would call it, but there is no explicit when-to-use statement, no prerequisites, and no exclusions relative to other reference-list tools.

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