Skip to main content
Glama

Query full name

query_full_name

Determine likely gender from a full 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": {
      "full_name": "<full_name>"
    },
    "name": "query_full_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
ipNo
localeNo
countryNo
full_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 burden. The single hedge word 'likely' usefully signals a probabilistic result rather than a certainty, but nothing is said about confidence scores, accuracy, rate limits, auth requirements, or how ambiguous or unmatched names behave.

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 efficient sentence with the action front-loaded and no wasted words. It is not under-specified for its length so much as simply short on detail the tool actually needs.

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?

No output schema and no annotations means the description is the only disclosure surface, yet it omits the four optional-looking parameters and says nothing about the shape or reliability of the response. For a 5-parameter classification tool, that is a meaningful gap.

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% across 5 parameters, yet the description only references full_name. The role of id, ip, locale, and country is left entirely undocumented anywhere, so the description does not compensate for the coverage 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: 'Determine likely gender from a full name,' and names the upstream endpoint (Gender-API v2 /gender). The 'full name' framing implicitly distinguishes it from the sibling query_first_name, but the description never names that alternative explicitly.

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?

No when-to-use guidance and no exclusions. With a sibling query_first_name present, an agent gets no instruction about when a full name is required versus a first-name lookup, nor what to do when no match is returned.

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