Skip to main content
Glama

List covered countries

list_countries
Read-onlyIdempotent

The 21 countries First Monday covers, with each one's ISO code, its open jobs, the open jobs new in the last 24 hours, and apart the jobs only probably open there.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
countriesYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered and the description does not contradict it. The description adds genuinely useful scope context (a fixed set of 21 countries, aggregated open-job counts including last-24-hours and 'probably open' job figures), but it does not say whether counts are live or cached, nor how often they refresh.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence is the right length for this tool, but the final clause ('and apart the jobs only probably open there') is garbled and forces the reader to re-parse what is being returned. The substance is front-loaded, but the wording reduces clarity.

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?

With an output schema present, the description need not spell out the return shape, and annotations cover the safety profile, so the essentials are covered. However, for a data-freshness-sensitive aggregation tool, the missing note on whether job counts are real-time leaves a meaningful gap.

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 there is nothing for the description to disambiguate and the baseline applies. No parameter-level confusion is possible.

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?

The description names the exact resource (the 21 countries First Monday covers) and enumerates the attributes returned, so an agent knows precisely what this tool yields. It lacks an explicit verb (list/retrieve) and does not note that it is unrelated to the job-oriented siblings, so it falls short of a 5.

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?

There is no guidance on when to call this versus alternatives, no mention of prerequisites, freshness, or caching. An agent must infer from the name alone that this is the lookup tool for country scope.

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.