Skip to main content
Glama

Query first name

query_first_name

Determine likely gender from a first name using the Gender-API v2 /gender endpoint.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "first_name": "<first_name>"
    },
    "name": "query_first_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
ipNo
localeNo
countryNo
first_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/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. It states the task and endpoint but does not disclose authentication needs, rate limits, error behavior, confidence levels, or what the response contains beyond the vague phrase 'likely gender'.

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 wasted wording. Its brevity is appropriate structurally, though it leaves important operational details unstated.

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?

The tool has five parameters, no output schema, no annotations, and no schema descriptions, so the description needs to do more to make the tool safely callable. It identifies the core input and endpoint but omits enough parameter meaning and behavioral context that an agent would be under-informed.

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% for five parameters, and the description only clarifies that first_name drives the gender inference. The roles of id, ip, locale, and country are not explained, so the description does not compensate for the low schema coverage.

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 gives a specific verb and resource: determine likely gender from a first name. It also names the Gender-API v2 endpoint, which makes the core operation clear, though it does not explicitly contrast itself with sibling tools such as query_full_name.

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?

Usage is only implied by the phrase 'from a first name'; there is no explicit when-to-use guidance, no when-not-to-use guidance, and no named alternative for full-name or email queries. An agent must infer that this tool is for first-name-only gender inference.

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