Skip to main content
Glama

fill_faces

Fill selected mesh boundaries with faces where possible to close gaps and complete surfaces in Blender.

Instructions

Fill selected boundary with faces where possible.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It never says that the tool mutates the mesh, whether the change is undoable, what happens to the boundary if filling fails, or what 'where possible' actually gates; only the word 'fill' implies a write.

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

Conciseness3/5

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

It is a single short sentence with no padding and the action is front-loaded, but brevity here comes at the cost of under-specification rather than being earned conciseness.

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

Completeness2/5

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

An output schema exists, so return values need not be explained. However, for a mesh-mutating operation with an undocumented required parameter and no annotations, the description omits the essentials: target object identification, selection requirements, and the failure condition implied by 'where possible'.

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% for the single required parameter 'name', and the description never says what 'name' refers to (object, mesh datablock, collection). With one undocumented parameter and no compensating text, the agent has no grounds for supplying a correct value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'fill' and object 'selected boundary' give a rough sense of a mesh-editing operation, but 'where possible' is vague and neither the 'name' parameter nor the affected mesh object is identified. It also does nothing to distinguish itself from the sibling 'inset_faces', which an agent could easily confuse with it.

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?

There is no statement of when to use this versus alternatives such as inset_faces, nor any prerequisites (edit mode, an active selection, which object). The only hint is the qualifier 'where possible', which does not tell the agent under what conditions the call succeeds.

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