Universal Database MCP

get_database_schema

Discover database tables, columns, primary keys, and foreign keys, filtered by your access role.

Instructions

Discover tables, columns, primary keys, and foreign-key relationships, filtered to only what your role is allowed to see.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`role`	No	One of "admin", "analyst", "support", "readonly_guest". Ignored (and taken from your access token instead) if the server is running with authentication enabled.
`db_uri`	No	Either a short connection name configured on the server (e.g. "prod", "reporting" — these map to environment variables like ANVAYA_DB_PROD, so no password is ever typed here), a full connection string for local testing (e.g. sqlite:///path/to/file.db), or left empty ("") to use the server's default database.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 13, 2026

TDQS

A3.5/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 full behavioral disclosure burden. It mentions role-based filtering but fails to describe output format, permissions required, potential errors, or how results are structured. The output schema exists but that doesn't excuse the lack of behavioral context.

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?

A single, well-structured sentence that front-loads the key action and enumerates returned data. No wasted words.

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

Completeness3/5

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

Given that there are no annotations and an output schema exists, the description should ideally explain more about behavior, such as caching, performance, or error handling. It covers the core purpose adequately but lacks depth for a tool with zero annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already fully documents both parameters. The description adds no parameter-specific information beyond what is in the schema, which meets the baseline of 3 for complete schema coverage.

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?

The description states a specific verb (Discover) and enumerates the exact resources returned (tables, columns, primary keys, foreign-key relationships). It clearly distinguishes itself from sibling tools like execute_safe_query, which run queries rather than introspect schema.

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

Usage Guidelines3/5

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

The description implies usage context via 'filtered to only what your role is allowed to see', suggesting it should be used to explore permitted schema. However, it provides no explicit when-to-use or when-not-to-use guidance relative to siblings such as explain_sql_query or execute_safe_query.

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

Deploy Server