Skip to main content
Glama
Sign In
CAD MCP Server

CAD MCP Server

by 652036
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_table_cell

Writes a value into a specified cell of a CAD drawing table using table ID, row, column, and content. Use it to update table data programmatically.

Instructions

Set a table cell value.

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": {
      "table_id": "<table_id>",
      "row": "<row>",
      "col": "<col>",
      "content": "<content>"
    },
    "name": "set_table_cell"
  }
}

Input Schema

NameRequiredDescriptionDefault
colYes
rowYes
contentYes
table_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/5.0
Behavior2/5

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

No annotations are provided, so the description must carry behavioral disclosure. 'Set' implies a mutation/overwrite, but it says nothing about persistence, error handling, indexing base, permissions, or effects on existing cell content.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is concise but insufficiently sized for a four-parameter mutation tool. It is front-loaded but under-specified, so the brevity reflects missing information rather than efficient structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given four required parameters, zero annotation coverage, no output schema, and 0% schema description coverage, the description is not complete enough to invoke the tool correctly. It omits indexing, table existence, content format, and overwrite semantics.

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

Parameters1/5

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

Schema description coverage is 0% and all four required parameters are undocumented in the schema. The description does not explain table_id, row, col, or content semantics such as zero-based indexing or overwrite behavior, so it adds no parameter meaning.

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?

Names a specific verb ('Set') and resource ('table cell value'), so the core operation is clear and distinct from most siblings like create_table. It stops short of differentiating from any other table-cell operation or clarifying scope, so not a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No when-to-use guidance is provided. It does not say a table must already exist, when to call this versus create_table, or how row/col are interpreted. Only the action itself is implied.

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