Skip to main content
Glama
mcp-geneanet

mcp-geneanet

by mgcrea

Geneanet: Status

geneanet_auth_status
Read-only

Reports server settings and, with check enabled, verifies Geneanet still answers both routes used, distinguishing a site change from a one-off failure. No credentials needed.

Instructions

Report the server's settings (default tree, request pacing) and, with check: true, whether Geneanet still answers both routes this server uses. No credentials are ever needed: everything read is public. Call this when a tool fails with a Cloudflare or markup error, to tell a site change from a one-off.

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

Input Schema

NameRequiredDescriptionDefault
checkNoAlso probe Geneanet: one site-wide search, plus one tree search when GENEANET_TREE is set. Two requests, about two seconds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds the non-obvious facts that no credentials are ever needed and everything read is public, which matters for a tool that contacts an external site. It also ties the probe to two specific routes, giving behavioral context the annotations cannot express.

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?

Two dense sentences with the primary output stated first and the conditional probe mode second, followed by the trigger condition. No filler or restatement of the name.

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 single-flag diagnostic tool with no output schema, the description says what is reported (default tree, request pacing, route health) and what it costs to check. Return shape details are not spelled out, but the essentials for calling it correctly are present.

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?

Schema coverage is 100%, so the sole boolean is already fully documented including request count and latency. The description still adds meaning by explaining what a successful probe signifies (both routes still answering), which goes slightly beyond the raw mechanics in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: reports server settings (default tree, request pacing) and optionally probes route health. The optional 'check: true' mode is called out directly, and the diagnostic framing distinguishes it from the sibling search/get tools that fetch actual records.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete trigger — call it when a tool fails with a Cloudflare or markup error — plus the intent behind that trigger (distinguish a site change from a one-off). It does not explicitly say when not to use it, but the failure-diagnosis context is clear enough to route the agent correctly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.