Skip to main content
Glama

validate_dbml

Read-only

Check DBML for syntax errors and semantic warnings like duplicate names, dangling references, and mismatched types before saving. Read-only validation that never modifies your schema.

Instructions

Parse DBML and report syntax errors plus semantic warnings (duplicate names, dangling refs, unrecognized/mismatched types) before saving it. Read-only — never touches the server.

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": {
      "dbml_source": "<dbml_source>"
    },
    "name": "validate_dbml"
  }
}

Input Schema

NameRequiredDescriptionDefault
dbml_sourceYesThe DBML text to check.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.4

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description's 'Read-only — never touches the server' mostly repeats structured data. It does add value by naming the semantic warning categories (duplicate names, dangling refs, unrecognized/mismatched types), but it does not describe the shape of the validation report.

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?

The description is two sentences, front-loaded with the tool's action and scope, and every clause contributes information about validation or usage timing.

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 simple one-parameter validation tool with complete schema coverage and annotations covering safety, the description gives enough context to call it correctly. It omits output format details, but the tool's simplicity and the description's warning categories make the omission minor.

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 one parameter with full schema description coverage ('The DBML text to check'), so the schema already carries parameter semantics. The description does not add format requirements, size limits, or examples beyond what the schema provides.

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 states a specific verb and resource: parse DBML and report syntax errors plus semantic warnings. It distinguishes validate_dbml from create/update workflows with 'before saving it,' but does not explicitly name or distinguish it from get_dbml_syntax_guide.

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?

The phrase 'before saving it' gives clear timing guidance for using validation ahead of a create/update operation. It does not state when not to use this tool or name alternatives such as get_dbml_syntax_guide.

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