Skip to main content
Glama

umlforge_erd_schema

Read-only

Design a database schema with ERD, integrity rules, and index recommendations. Provides entity diagrams, schema narrative, and N+1 risk flags.

Instructions

Design a database schema with ERD, integrity rules, and index recommendations.

USE THIS WHEN:

  • You are designing or reviewing a database schema

  • You need an ERD with foreign keys, cardinality, and data types

  • You want index recommendations and N+1 risk flags

NOT FOR:

  • Full codebase analysis (which may include DB) → use umlforge_reverse_engineer

  • API flows between services → use umlforge_api_sequence

  • Event-driven data pipelines → use umlforge_event_driven

Produces:

  • erDiagram: entities with typed attributes, cardinality, FK labels

  • Schema narrative: one paragraph per entity — purpose, index recommendations, denormalisation decisions

  • Data integrity checklist: uniqueness, FK integrity, null policies, constraints

  • N+1 query risk flags

  • (report_mode=True) Design Score: Normalisation, Query Performance, Data Integrity (A–F)

Args: domain_description: What the database stores (e.g. "E-commerce: users, products, orders, payments"). entities: Known entities and key attributes (e.g. "User(id, email, tier), Order(id, user_id, status, total)"). access_patterns: Most frequent read/write queries (optional — used for index recommendations). db_technology: Database technology (default: PostgreSQL). report_mode: True → also produce a Design Score report. Pro/Team/Enterprise only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entitiesYes
report_modeNo
db_technologyNoPostgreSQL
access_patternsNo
domain_descriptionYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, indicating no state changes. The description reinforces this by stating it 'designs' and 'produces' a schema without modifying data. It also discloses the Pro/Team/Enterprise restriction on report_mode, which is a behavioral constraint not present in annotations. No contradictions.

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 well-organized into sections with headings and bullet points. It front-loads the primary purpose, then provides usage context, output details, and parameter descriptions. Every sentence adds value without redundancy. It is appropriately sized for the tool's complexity.

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?

Given the tool's complexity (5 parameters, output schema present), the description covers all essential aspects: purpose, usage boundaries, behavioral constraints, parameter semantics, and output expectations. It addresses the 'contextual completeness' dimension fully for this tool.

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

Parameters5/5

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

Despite 0% schema description coverage, the description includes a dedicated 'Args' section that explains each parameter's purpose, examples, and defaults. For example, 'domain_description: What the database stores' and 'report_mode: True → also produce a Design Score report. Pro/Team/Enterprise only.' This fully compensates for the schema's lack of descriptions.

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 opens with a clear verb and resource: 'Design a database schema.' It distinguishes from siblings through the 'NOT FOR' section, explicitly naming alternative tools (umlforge_reverse_engineer, umlforge_api_sequence, umlforge_event_driven). The purpose is specific and unambiguous.

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?

The description includes explicit 'USE THIS WHEN' and 'NOT FOR' sections, providing clear context for when to invoke the tool and when to choose a sibling. It gives concrete conditions and directs to alternatives, leaving no ambiguity for the agent.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dave1362/umlforge-connector'

If you have feedback or need assistance with the MCP directory API, please join our Discord server