Skip to main content
Glama

native_create

Destructive

Creates a new experimental empty native .pdsprj inside an existing semantic project, then verifies the generated instance using project_open and save.

Instructions

Create a NEW experimental empty native .pdsprj within an existing semantic project. No UI input. Use project_open/save to verify the generated instance.

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

Input Schema

NameRequiredDescriptionDefault
projectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=false, so the safety profile is covered. The description adds real context — the output is an empty, experimental artifact and there is no UI input — but it never explains what destructiveHint=true means in practice, e.g. whether an existing file is overwritten or whether the operation is reversible.

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

Conciseness4/5

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

Three short sentences with the core action front-loaded and zero filler. The verification hint earns its place; the "No UI input" fragment is slightly cryptic but cheap.

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

Completeness3/5

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

For a one-parameter, no-output-schema factory tool this covers the essentials: what is created, the precondition, and how to validate the result. The gaps are the naming/location of the generated file and the concrete meaning of the destructive flag, both of which matter for a write operation.

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 description coverage is 0% for the single parameter, so the description must carry the meaning, and it does clarify that "project" refers to the existing semantic project that will contain the new file. It does not explain how the new .pdsprj is named or where it is placed, leaving the only parameter partially specified.

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?

"Create a NEW experimental empty native .pdsprj within an existing semantic project" names a specific verb (create) and a precisely scoped resource (an empty .pdsprj inside an existing semantic project). It is distinguishable from native_apply or native_check by the artifact it produces, though it never explicitly contrasts itself with the similarly named project_create sibling.

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 states a prerequisite (an existing semantic project must already exist) and a follow-up workflow ("Use project_open/save to verify the generated instance"), which is genuine when-and-how guidance. It stops short of saying when to prefer this over project_create or what to do if the target already exists.

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