partme_blender

Overview Schema Source Related Servers Discussions Admin

capability.list

blender_capability_list

Read-onlyIdempotent

List available Blender capabilities on the partme_blender MCP server. Filter results by domain, platform, runtime, or profile to identify which guarded operations are supported for your current session.

Instructions

PartMe Blender Harness command capability.list. Risk: read; maturity: L3. Requirements: Per-request argument checks and session policy still apply

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`domain`	No
`offset`	No	Three finite numbers; rotation uses radians
`profile`	No
`runtime`	No
`maturity`	No
`platform`	No
`_requestId`	No	Stable request id for replay safety
`runtimeMode`	No
`_authorization`	No	Action-bound Harness authorization claim
`_transactionId`	No	Harness milestone transaction id
`blenderVersion`	No
`_expectedSceneRevision`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed18 schema fields changedv0.5.3Sep 22, 2026

removedInput schema / properties / blenderVersion / description

Removed value: -"See command validation; detailed type not yet audited"

addedInput schema / properties / blenderVersion / items

Added value: +{
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / blenderVersion / maxItems
```
Added value: +3
```
addedInput schema / properties / blenderVersion / minItems
```
Added value: +3
```
addedInput schema / properties / blenderVersion / type
```
Added value: +"array"
```

removedInput schema / properties / platform / description

Removed value: -"See command validation; detailed type not yet audited"

addedInput schema / properties / platform / type
```
Added value: +"string"
```
addedInput schema / properties / profile / additionalProperties
```
Added value: +false
```

removedInput schema / properties / profile / description

Removed value: -"See command validation; detailed type not yet audited"

addedInput schema / properties / profile / properties

Added value: +{
+  "excludeClasses": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "excludeDomains": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+}

addedInput schema / properties / profile / type
```
Added value: +"object"
```
addedInput schema / properties / runtime / additionalProperties
```
Added value: +false
```

removedInput schema / properties / runtime / description

Removed value: -"See command validation; detailed type not yet audited"

addedInput schema / properties / runtime / properties

Added value: +{
+  "architecture": {
+    "type": "string"
+  },
+  "blenderVersion": {
+    "items": {
+      "minimum": 0,
+      "type": "integer"
+    },
+    "maxItems": 3,
+    "minItems": 3,
+    "type": "array"
+  },
+  "platform": {
+    "type": "string"
+  },
+  "runtimeMode": {
+    "type": "string"
+  }
+}

addedInput schema / properties / runtime / required

Added value: +[
+  "blenderVersion",
+  "platform",
+  "architecture",
+  "runtimeMode"
+]

addedInput schema / properties / runtime / type
```
Added value: +"object"
```

removedInput schema / properties / runtimeMode / description

Removed value: -"See command validation; detailed type not yet audited"

addedInput schema / properties / runtimeMode / type
```
Added value: +"string"
```

First observedv0.1.0Sep 15, 2026

TDQS

D1.3/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds 'Risk: read' (redundant) and 'maturity: L3' plus a generic requirement note. It doesn't describe what the tool returns, side effects, or any behavioral details beyond what annotations already cover. No contradiction, but minimal added value.

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 description is extremely short (one sentence) but this is under-specification, not conciseness. It omits essential information and is not front-loaded with useful details. It reads like a metadata stub rather than a helpful guide.

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?

With 13 parameters, nested objects, and an output schema, the description is grossly inadequate. It doesn't explain the tool's purpose, parameter semantics, or expected output. An agent would have no idea what capabilities are being listed or how to invoke it correctly.

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?

The description provides no information about any of the 13 parameters. With schema description coverage at only 31%, many parameters are undocumented in the schema, and the description does nothing to compensate. It fails to explain purpose or format of parameters like limit, domain, offset, or nested objects.

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

Purpose1/5

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

The description merely restates the command name 'capability.list' without stating what it does. It doesn't say it lists capabilities, nor does it distinguish itself from sibling tools like blender_capability_describe or blender_session_capabilities. It fails to provide a clear verb+resource or purpose.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus alternatives. No mention of scenarios, prerequisites, or exclusions. The description gives no context for selection.

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

Deploy Server