Connhex MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

Create Manufacturing Resource

create_manufacturing_resource

Create a manufacturing resource in Connhex using schema-defined attributes and optional relationships. Call get_schema first to discover valid fields.

Instructions

Create a new resource on a Connhex JSON:API service.

Use schema fields for attributes and relationships.

If available, call the get_schema tool first to discover valid resource types, attributes, and relationships.

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": {
      "resource_type": "<resource_type>",
      "attributes": "<attributes>"
    },
    "name": "create_manufacturing_resource"
  }
}

Input Schema

Name	Required	Description
`attributes`	Yes	Resource attributes payload. Field names must come from get_schema.
`relationships`	No	Optional JSON:API relationships payload.
`resource_type`	Yes	Resource type name from get_schema, e.g. "devices" or "plants".

Output Schema

Name	Required	Description	Default
`id`	Yes
`type`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0Jul 7, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already indicate readOnlyHint=false (write) and destructiveHint=false. The description confirms it creates a new resource, which aligns with the annotations. However, it adds no further behavioral details such as side effects, authorization requirements, or response behavior, so it doesn't significantly enhance transparency beyond the annotations.

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?

The description is three sentences, each delivering distinct information: purpose, parameter usage, and prerequisite tool. No redundant or irrelevant content. It is appropriately front-loaded with the main action.

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?

Given the presence of an output schema (context signals indicate 'has output schema: true'), the description does not need to explain return values. It covers the purpose, parameter semantics, and a key prerequisite. A small gap remains regarding error handling or success confirmation, but overall it is adequately complete for a creation tool.

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?

All three parameters are described in the input schema, and the description adds meaningful context: for `attributes`, it states 'Field names must come from get_schema'; for `resource_type`, it references `get_schema` for valid values; and for `relationships`, it notes it's optional JSON:API payload. This enriches the schema definitions and guides correct usage.

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

Purpose4/5

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

The description clearly states the tool creates a new resource on a Connhex JSON:API service. The verb 'create' and resource type are explicit. Although the name includes 'manufacturing', the description does not differentiate it from the sibling 'create_resource' tool, but the specificity of the name and the JSON:API context provide sufficient clarity.

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?

The description advises users to call `get_schema` first to discover valid resource types, attributes, and relationships, which serves as a clear prerequisite. It guides the user on how to use the tool effectively, though it lacks explicit when-not-to-use scenarios or alternatives.

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