Skip to main content
Glama
Sign In
Archicad MCP Connector

Archicad MCP Connector

by davidharutyunyan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Delete custom Project Info fields

delete_project_info_fields
Destructive

Deletes custom Project Info fields by database key or exact name in Archicad. Built-in fields cannot be removed, so clear their values instead.

Instructions

Deletes CUSTOM Project Info fields (category Custom) by database key or name. Built-in fields cannot be deleted (set their value to "" instead). Returns [{key, deleted} | {error}].

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": {
      "fields": "<fields>"
    },
    "name": "delete_project_info_fields"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsYesKeys ('autotext-<GUID>') or exact names of custom fields

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already mark this destructive and non-idempotent, so the safety profile is covered. The description adds meaningful behavioral context beyond that: only Custom-category fields are eligible, built-ins are rejected, and the return shape is [{key, deleted} | {error}], which tells the agent deletions are per-field and may partially fail rather than being atomic.

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?

Three short sentences, front-loaded with the scope constraint, then the exclusion rule, then the return contract. No filler and nothing buried.

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?

No output schema exists, and the description compensates by describing the return shape; the error/partial-success case is implied by the union type. What remains thin is whether prior state matters for repeated calls, but for a single-parameter delete this is close to complete.

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 coverage is 100% and the single parameter is fully documented with key format ('autotext-<GUID>') and exact-name matching. The description's 'by database key or name' essentially restates the schema, so baseline 3 is appropriate.

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?

States a specific verb (deletes), resource (Project Info fields), and a hard scope qualifier (CUSTOM / category Custom) that separates it from sibling get_project_info_fields and set_project_info_fields as well as from delete_attributes and delete_property_definitions. An agent can identify the target of the operation without opening the schema.

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?

Explicitly states when the tool does NOT apply (built-in fields cannot be deleted) and gives the alternative action for that case (set their value to ""). This is real routing guidance, though it does not name a sibling tool for the built-in-field case or describe ordering/prerequisite requirements.

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