MaxMindDB MCP Server

Overview Schema Source Related Servers Discussions Admin

Inspect a database

inspect_database

Read-onlyIdempotent

Read MMDB metadata and sample field paths, types, and examples. Use this to choose fields, filter paths, or a summarize_network group_by field. Sampling starts at the first network record, so observed fields are not a complete schema.

Instructions

Input Schema

Name	Required	Description	Default
`database`	Yes	Exact filename of a loaded database from list_databases.
`sample_size`	No	Maximum network records to sample. Larger samples may reveal more fields. Sampling can stop early at internal field limits.

Output Schema

Name	Required	Description
`fields`	Yes
`database`	Yes
`metadata`	Yes
`sample_limit`	Yes	Requested record sampling limit. Field traversal limits may stop sampling earlier.
`sampled_records`	Yes	Network records sampled in database order, not a statistically representative sample.
`schema_complete`	Yes	Always false. A field absent from this sample may exist in other records.
`fields_truncated`	Yes	True when field traversal limits or unaddressable keys omitted fields. Does not indicate whether all records were sampled.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.4.0Oct 22, 2026

addedOutput schema / properties / fields_truncated / description

Added value: +"True when field traversal limits or unaddressable keys omitted fields. Does not indicate whether all records were sampled."

addedOutput schema / properties / metadata / properties / build_epoch / description
```
Added value: +"Database build time in Unix seconds."
```

addedOutput schema / properties / metadata / properties / node_count / description

Added value: +"Number of search-tree nodes, not the count of data records or networks."

addedOutput schema / properties / metadata / properties / record_size / description
```
Added value: +"Size in bits of each search-tree record."
```

addedOutput schema / properties / sample_limit / description

Added value: +"Requested record sampling limit. Field traversal limits may stop sampling earlier."

addedOutput schema / properties / sampled_records / description

Added value: +"Network records sampled in database order, not a statistically representative sample."

addedOutput schema / properties / schema_complete / description

Added value: +"Always false. A field absent from this sample may exist in other records."

Changed2 schema fields changedv0.3.1Oct 18, 2026

addedInput schema / properties / database / description

Added value: +"Exact filename of a loaded database from list_databases."

addedInput schema / properties / sample_size / description

Added value: +"Maximum network records to sample. Larger samples may reveal more fields. Sampling can stop early at internal field limits."

First observedv0.1.0Oct 18, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: sampling begins at the first network record and observed fields are not a complete schema, which prevents the agent from over-trusting results.

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?

Three short sentences, all front-loaded with the core action first, then usage routing, then the sampling caveat. Every sentence earns its place with no restatement of the name or schema.

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

Completeness5/5

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

An output schema exists, so return values need no explanation. Combined with full parameter coverage and annotations, the description supplies everything an agent needs: what it reads, when to use it, the sampling limitation, and where to go for integrity checks.

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 baseline is 3, but the description adds meaning beyond the schema by noting that sampling starts at the first record — a non-random starting point that affects how sample_size should be interpreted and how representative the results are.

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?

Specific verb+resource: 'Read MMDB metadata and sample field paths, types, and examples.' It also distinguishes itself from siblings by naming summarize_network (group_by field selection) and verify_database (integrity), so an agent can route without opening other schemas.

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

Usage Guidelines5/5

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

Explicit when-to-use: 'Use this to choose fields, filter paths, or a summarize_network group_by field.' It also names an exclusion case by directing integrity checks to verify_database instead.

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

Deploy Server