Skip to main content
Glama

Query email address

query_email

Extract a likely first name from an email address and determine likely gender 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": {
      "email": "<email>"
    },
    "name": "query_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
ipNo
emailYes
localeNo
countryNo

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?

With no annotations, the description carries the full behavioral burden. It does disclose something useful: results are 'likely' (probabilistic inference) and come from the external Gender-API v2 /gender endpoint, hinting at a third-party dependency. But it says nothing about API key/auth requirements, rate limits, cost, failure modes, or what happens with ambiguous or role-based addresses (e.g. info@).

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 tight sentence that front-loads the two outputs before naming the backend endpoint. Nothing is wasted, though the endpoint reference is arguably less useful to an agent than the undocumented parameter behavior would have been.

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?

For a 5-parameter tool with no annotations, no output schema, and zero schema description coverage, the description is too thin. It never states the return shape (score, confidence, gender value set) and leaves four parameters undocumented, so an agent cannot call it confidently beyond the required email field.

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, so the description must compensate and does not. It mentions only 'email'; id, ip, locale, and country are entirely unexplained, even though locale and country plausibly affect gender inference accuracy. This is a significant gap for a lookup whose quality depends on those hints.

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 uses specific verbs ('extract', 'determine') tied to the resource (an email address) and names the two outputs: likely first name and likely gender. That is far clearer than the bare name 'query_email'. It does not, however, distinguish this from siblings like query_first_name or query_full_name, which an agent could reasonably confuse it with.

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?

There is no guidance on when to choose this over query_first_name or query_full_name, nor any stated prerequisites. The agent must infer that this tool is for the case where only an email is available and both name and gender are wanted. No exclusions or conditions are given.

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