Skip to main content
Glama

Get country of origin

get_country_of_origin

Determine the likely country of origin for a first name, full name, or email via Gender-API v2 /country-of-origin.

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

Input Schema

NameRequiredDescriptionDefault
idNo
emailNo
full_nameNo
first_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it only says the result is a 'likely' country and references Gender-API v2. It does not disclose read-only status, authentication needs, rate limits, error behavior, or what happens when no parameters are supplied.

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?

The description is a single front-loaded sentence with no filler and clearly identifies the operation. It is perhaps too sparse for a four-parameter tool with no annotations, but the wording itself is efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given four optional parameters, zero schema descriptions, no annotations, and no output schema, the definition is materially incomplete. It does not explain parameter selection, API behavior, or return characteristics.

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?

Schema description coverage is 0%, and the description only mentions first name, full name, and email while omitting the id parameter. It also does not explain optionality, input precedence, or whether at least one of these fields must be provided.

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 states a specific verb and resource: determine the likely country of origin for a first name, full name, or email. It is clear what the tool does, but it does not explicitly differentiate itself from similarly named siblings such as query_email or query_first_name.

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 listed input types imply when the tool is applicable, but there is no explicit guidance on alternatives, exclusions, or prerequisites. It does not explain how to choose this tool over related query tools.

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.

Resources