Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

country_all

Read-onlyIdempotent

Retrieve all countries from REST Countries, optionally limiting results to specified fields, to populate country datasets or support location-based workflows.

Instructions

Get all countries from REST Countries.

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

Input Schema

NameRequiredDescriptionDefault
fieldsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

B3/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so safety is covered. The description adds nothing beyond that: no note on response size (~250 countries), whether responses are paginated, or what 'fields' does to the output, so it earns little credit for behavioral depth.

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?

A single front-loaded sentence with no waste; it is appropriately sized for a trivial read tool but has room to carry one more clause about output shape or the fields parameter.

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?

For a simple no-arg-required listing tool with no output schema, the description covers the basic contract but leaves two agent-relevant gaps: what 'fields' accepts and roughly how large the response is. Adequate, not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single optional 'fields' parameter has 0% schema description coverage and is never mentioned in the description, so an agent has no way to know it likely projects/filters returned properties. With one undocumented param, the description does not compensate for the schema gap.

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?

States a specific verb and resource ('Get all countries') and names the upstream source (REST Countries), which is enough to distinguish it from the filtered siblings like country_by_name or country_by_region. It stops short of explicitly contrasting with those siblings, but the 'all' scope is unambiguous.

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?

The word 'all' implicitly signals this is the bulk-listing option versus the per-country siblings, but the description never says when to choose it or when a narrower lookup would be better. Usage is inferable rather than stated.

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