Skip to main content
Glama
StructlyOfficial

Structly MCP Server

Official

create_relationship

Create a foreign key relationship between two columns in a schema, with configurable relationship type and delete/update behaviors.

Instructions

Создать связь (внешний ключ) между двумя колонками.

    Args:
        schema_uuid: UUID схемы.
        source_table_uuid: UUID исходной таблицы.
        source_column_uuid: UUID исходной колонки (FK-сторона).
        target_table_uuid: UUID целевой таблицы (PK-сторона).
        target_column_uuid: UUID целевой колонки (PK-сторона).
        relationship_name: Название связи.
        relationship_type: Тип связи (например, one_to_many, many_to_many).
        delete_action: Действие при удалении: CASCADE, SET NULL, SET DEFAULT,
            RESTRICT или NO ACTION.
        update_action: Действие при обновлении: CASCADE, SET NULL, SET DEFAULT,
            RESTRICT или NO ACTION.
        branch_name: Ветка схемы (по умолчанию main).
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
branch_nameNomain
schema_uuidYes
delete_actionYes
update_actionYes
relationship_nameYes
relationship_typeYes
source_table_uuidYes
target_table_uuidYes
source_column_uuidYes
target_column_uuidYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

Annotations are missing, so the description carries the full burden. It mentions 'create' (a mutation) but does not disclose side effects, permissions, or the impact on the schema. This is a notable gap for a creation tool.

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?

The description opens with a concise purpose sentence followed by a structured docstring. While it is long due to 10 parameters, the content is necessary given zero schema descriptions and avoids unnecessary prose.

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?

The description covers all parameters with explanations and examples, making it sufficient for invoking the tool correctly. However, it does not mention side effects or the need to commit changes, which might be relevant context for a schema-modifying operation.

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?

The input schema has zero descriptions for its 10 parameters (0% coverage). The docstring compensates by explaining each parameter's role, clarifying FK/PK sides, providing examples for relationship_type, and enumerating delete/update actions. This adds meaningful semantic information beyond the schema.

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 clearly states that this tool creates a relationship (foreign key) between two columns. It uses a specific verb and resource, distinguishing it from siblings like delete_relationship and edit_relationship.

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 by defining the action, but it does not explicitly state when to use this tool versus alternatives or mention any exclusions. The parameter list gives context for how to use it, but no explicit guidance.

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/StructlyOfficial/MCP-server'

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