MCP Platform Service

create_entity

Add a new entity to the external platform by specifying its type (user, project, task, or document) and data.

Instructions

Create a new entity in the external platform

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": {
      "entityType": "<entityType>",
      "data": "<data>"
    },
    "name": "create_entity"
  }
}

Input Schema

Name	Required	Description	Default
`data`	Yes	The entity data to create
`entityType`	Yes	The type of entity to create

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 6, 2026

TDQS

B3/5.0

Behavior2/5

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

With no annotations provided, the description must explain behavioral traits, but it only states 'Create a new entity'. It does not disclose side effects, idempotency, required permissions, or what happens upon success or failure. The agent gets no insight into the tool's behavior beyond the plain action.

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?

The description is a single sentence, which is concise, but it is too terse and lacks useful information. While it wastes no words, it also fails to fill the minimal information needed for effective tool use.

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?

Given the tool has two parameters (one enum, one nested object) and no output schema, the description should provide additional context like expected return values, error handling, or authentication. It does not, leaving the agent underinformed for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for both parameters. The description adds no additional meaning beyond the schema, such as clarifying the structure of the 'data' object or providing examples. Baseline 3 is maintained because the schema already documents parameters adequately.

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?

The description clearly states the action 'Create' and the resource 'new entity', which is distinct from sibling tools like 'delete_entity', 'get_entity', and 'update_entity'. It leaves no ambiguity about what the tool does.

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?

The description provides no guidance on when to use this tool versus alternatives, such as prerequisites, authentication requirements, or when creation might fail. It gives no context about use cases or exclusions.

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

Deploy Server