Skip to main content
Glama
putervision

world-model-mcp

by putervision
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

manage_spatial_spec

Manage spatial baseline contracts: set constraints, verify live entities read-only, list specs. Validates physical contracts without mutating entity state.

Instructions

Manage Spatial Spec-Driven Development (Spatial SDD) physical baseline contracts. Actions: set (registers a baseline spec), verify (evaluates live entities against constraints without mutating), list (returns all registered specs). verify is read-only. set persists constraints. Returns {ok, action, spec_id, passed:boolean, violations[]}. Use manage_spatial_spec instead of update_entity when validating physical contract baselines rather than mutating live entity state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoName of the spatial specification
actionNoAction to perform (default: list)
boundsNoSpatial bounding box limits
projectNoOptional project identifier
toleranceNoVerification tolerance percentage (default: 0.05)
constraintsNoList of spatial constraints
descriptionNoSpecification description
sdd_requirement_idNoLinked state-memory SDD requirement node ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.1
    • addedInput schema / properties / action / enum
      Added value: +[
+  "set",
+  "verify",
+  "list"
+]
  2. Changed7 schema fields changedv0.4.1
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / action / enum
      Removed value: -[
-  "set",
-  "verify",
-  "list"
-]
    • removedInput schema / properties / bounds / additionalProperties
      Removed value: -true
    • removedInput schema / properties / bounds / properties / max / additionalProperties
      Removed value: -true
    • removedInput schema / properties / bounds / properties / min / additionalProperties
      Removed value: -true
    • removedInput schema / properties / constraints / items / additionalProperties
      Removed value: -true
  3. First observedv0.3.1

TDQS

A4.6/5.0
Behavior4/5

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

Annotations are tool-level (readOnlyHint=false, destructiveHint=false, idempotentHint=false) and the description adds the crucial per-action nuance that verify is read-only while set persists constraints. It also discloses the return shape {ok, action, spec_id, passed, violations[]} in the absence of an output schema. It stops short of covering overwrite/idempotency behavior for repeated 'set' calls or any permission requirements.

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 resource and action list, then mutation semantics, return shape, and the sibling disambiguation — every sentence carries distinct information with no filler.

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 an 8-parameter, nested-object tool with no output schema, the description covers action set, mutation semantics, return shape, and routing to the right sibling. Gaps remain around re-set/idempotency behavior and the meaning of the 'custom' constraint and 'tolerance' percentage.

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 100%, so the baseline is 3; the description adds value by tying parameters to actions (constraints and baseline registration belong to 'set', live-entity evaluation belongs to 'verify'). It does not explain tolerance semantics, the 'custom' constraint type, or which params each action requires, so it stays just above baseline.

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 resource (Spatial SDD physical baseline contracts) and enumerates the three concrete actions with one-line semantics for each, so an agent knows exactly what the tool does. It also names the sibling it should not be confused with (update_entity), making it distinguishable without opening either schema.

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

Usage Guidelines5/5

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

Provides an explicit routing rule: 'Use manage_spatial_spec instead of update_entity when validating physical contract baselines rather than mutating live entity state.' It also disambiguates the internal actions (verify is non-mutating, set persists), giving both when-to-use and when-not-to-use guidance.

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