Skip to main content
Glama
Sign In
FauxGen MCP

FauxGen MCP

by LazyInvestor
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List countries

list_countries

Fetch all FauxGen country codes, dial codes, and country page URLs. Use it to browse supported countries and access their pages.

Instructions

List all FauxGen country codes with dial codes and country page URLs.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. 'List' strongly implies a read-only, non-mutating, no-arg operation, and the description discloses the return contents (codes, dial codes, page URLs), which is genuinely useful given there is no output schema. It stops short of stating format, ordering, or whether the list is paginated or static.

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?

One sentence, no filler, and the key noun (FauxGen country codes) is front-loaded immediately after the verb.

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 lookup with no output schema, the description usefully enumerates what comes back, which is the main thing an agent needs. Only the return format and list ordering/coverage are unspecified.

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. Baseline of 4 applies for a parameterless tool.

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 (List) and resource (FauxGen country codes) and even names the payload contents (dial codes, country page URLs). It reads clearly as a reference/lookup tool, distinct from the generate_* siblings, though it never explicitly contrasts itself with them.

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?

There is no explicit when-to-use guidance or named alternative, but 'List all FauxGen country codes' implies the obvious role: fetching codes to feed other tools. 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