Skip to main content
Glama
Sign In

QuintaDB

by ua.com.quintadb
OverviewDiscussionsAdmin

set_column_size

Idempotent

Change the width of a column in the table or inside a subform/linked_records. Use it when the user asks to make a column wider/narrower, to enlarge/shrink a column in the table view.

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": {
      "app_id": "<app_id>",
      "entity_id": "<entity_id>",
      "field_id": "<field_id>",
      "size": "<size>"
    },
    "name": "set_column_size"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeYesNew width in pixels (for example 200)
app_idYesProject ID
field_idYesID of the column field whose width changes
entity_idYesID of the form whose table changes
subform_field_idNoIf the column changed is INSIDE a subform or linked_records, pass the ID of the subform field (linked_records/subform) here. Without this parameter the column of the main table changes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / app_id / description
      Previous value: -"ID проєкту"New value: +"Project ID"
    • changedInput schema / properties / entity_id / description
      Previous value: -"ID форми, таблиця якої міняється"New value: +"ID of the form whose table changes"
    • changedInput schema / properties / field_id / description
      Previous value: -"ID поля-колонки, ширину якої міняємо"New value: +"ID of the column field whose width changes"
    • changedInput schema / properties / size / description
      Previous value: -"Нова ширина в пікселях (наприклад 200)"New value: +"New width in pixels (for example 200)"
    • changedInput schema / properties / subform_field_id / description
      Previous value: -"Якщо міняємо колонку ВСЕРЕДИНІ субформи або linked_records — передай сюди ID поля-субформи (linked_records/subform). Без цього параметра міняється колонка в основній таблиці."New value: +"If the column changed is INSIDE a subform or linked_records, pass the ID of the subform field (linked_records/subform) here. Without this parameter the column of the main table changes."
  2. Added

TDQS

A3.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, covering the safety profile. The description adds no behavior beyond that: nothing about persistence, whether other users' views are affected, or whether the change survives a refresh. The subform targeting it mentions is already spelled out in the schema.

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?

Two sentences, purpose first, trigger second, with zero filler. Sized appropriately for a narrow single-property setter.

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?

A simple, idempotent, non-destructive column setter with full schema coverage and declarative annotations needs little more than this. The only real gap is the absence of any persistence or view-scope note, which is minor here.

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 all five parameters, including the subform_field_id targeting rule, are already documented in the schema. The description adds no units, ranges, or defaults beyond the schema's 'New width in pixels (for example 200)', so the baseline 3 applies.

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?

States a specific verb and resource: change the width of a column, and scopes it to the table or a subform/linked_records table. That is enough to tell it apart from update_field or reorder_fields, 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 Guidelines4/5

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

Gives a concrete trigger ('Use it when the user asks to make a column wider/narrower, to enlarge/shrink a column in the table view'), which reliably maps user intent to this tool. It does not state exclusions or point to an alternative tool, so it stops short of a full routing decision.

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

All QuintaDB toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources