Skip to main content
Glama

Declare Intent

declare_intent
Destructive

Record a part's functional invariants so they can be re-checked after every edit, preventing unintended geometry changes. Stores one replaceable contract per part in the .FCStd file.

Instructions

Record the functional invariants a part must keep satisfying, so they can be re-checked after every edit (see verify_intent). Persists in the .FCStd as a JSON property bag (AD_Intent); one contract per part — re-declaring replaces.

handle: the part. contract: a dict with any of these (declare at least one): watertight (bool) require check_shape's watertight_solid verdict. airtight_path (dict) {inlet, outlet, min_aperture_mm2?}; each port is a face tag / 'FaceN' / int / declared role-or-name. required_faces (list) face tags / 'FaceN' / declared role-or-names that must still resolve (catches a deleted/drifted face).

Returns {handle, contract} — the stored contract.

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": {
      "handle": "<handle>",
      "contract": "<contract>"
    },
    "name": "declare_intent"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYes
contractYes
workspaceNoRun this call in this named workspace

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description adds real value beyond them: it discloses the storage mechanism (.FCStd JSON property bag AD_Intent) and that re-declaring overwrites the single existing contract, which is exactly the destructive behavior an agent needs to know. It does not cover permissions or failure modes, keeping it short of a 5.

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?

Front-loaded with the purpose and persistence model, then a compact bulleted enumeration of contract keys. No filler sentences; every line carries either behavior or parameter semantics.

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?

For a mutation tool with nested-object params and no output schema, the description covers what is stored, the replacement behavior, the valid contract keys, and the return shape ({handle, contract}). Only the workspace parameter and handle format are left implicit, which the schema partially covers.

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?

Schema description coverage is only 33%, so the description must compensate, and it does: the contract dict's allowed keys (watertight, airtight_path with inlet/outlet/min_aperture_mm2, required_faces) are documented with types and accepted value forms, which the schema's bare object type does not convey. The handle parameter is only glossed as 'the part', and the workspace param is left to 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?

States a specific verb and resource ('Record the functional invariants a part must keep satisfying') and immediately names the paired sibling verify_intent, so an agent can place it in the intent/verify workflow without opening any schema. It also distinguishes it from declare_performance-style tools by scoping to per-part functional contracts.

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?

Clearly frames when to use it ('so they can be re-checked after every edit') and points at verify_intent as the consumer. The replacement semantics ('one contract per part — re-declaring replaces') give an important usage constraint, though there is no explicit when-not-to-use or prerequisite call ordering.

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