Skip to main content
Glama

mnemon_get_schema

Retrieve database table structures, column data types, and primary key constraints for a specified tenant to understand or validate schema.

Instructions

Introspect database schema tables, column types, and primary key constraints.

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": {
      "tenant_id": "<tenant_id>"
    },
    "name": "mnemon_get_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
tenant_idYesDatabase tenant identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden. "Introspect" hints at a read-only operation, but nothing confirms it is non-destructive, states whether it requires elevated tenant permissions, or indicates whether the entire schema is returned at once (potentially large) versus scoped to a single table.

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?

One well-formed sentence with the resource list front-loaded and no filler words. It is appropriately sized for the amount of information conveyed, though that brevity leaves behavioral gaps unaddressed.

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?

For a simple one-parameter introspection tool with no output schema, the description covers the broad shape of what comes back (tables, columns, PK constraints). It falls short on scope and volume: whether all tables are returned, whether system schemas are included, and what the response structure looks like.

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?

There is a single parameter, tenant_id, and the schema already documents it at 100% coverage as the "Database tenant identifier." The description adds no further meaning such as whether the tenant must be active or whether cross-tenant introspection is possible, so the schema does all the work.

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 a specific verb ("Introspect") and names the exact resources returned: tables, column types, and primary key constraints. That distinguishes it reasonably from mnemon_reconcile_schema and mnemon_execute_sql, though it never names those siblings explicitly.

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?

Usage is only implied: an agent can infer this is the discovery step before writing SQL or reconciling schemas. There is no explicit statement of when to prefer this over mnemon_reconcile_schema or mnemon_diff_branch, and no prerequisites beyond the required tenant_id.

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

Deploy Server

Other Tools