Skip to main content
Glama

import_project

Import a portable project configuration JSON string (previously produced by export_project) to create a new project workspace and bulk-populate all of its collections, mock endpoints, and conditional rules. Returns the newly created project details including its assigned projectId and slug.

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

Input Schema

NameRequiredDescriptionDefault
dataYesComplete exported project JSON string (from export_project) containing 'name', 'description', and 'collections'.
nameNoOptional override name for the newly imported project (defaults to the 'name' field inside the exported JSON data if omitted).
descriptionNoOptional override description for the newly imported project (defaults to the exported description if omitted).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / data / description
      Previous value: -"Exported project JSON string representation"New value: +"Complete exported project JSON string (from export_project) containing 'name', 'description', and 'collections'."
    • changedInput schema / properties / description / description
      Previous value: -"New project description"New value: +"Optional override description for the newly imported project (defaults to the exported description if omitted)."
    • changedInput schema / properties / name / description
      Previous value: -"New project name (optional, defaults to exported name if empty)"New value: +"Optional override name for the newly imported project (defaults to the 'name' field inside the exported JSON data if omitted)."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the key write behavior: a new project workspace is created and collections, mocks, and rules are bulk-populated. It also states what is returned (projectId and slug), which matters without an output schema. Gaps remain around failure handling (invalid or partial JSON), idempotency/duplicate creation, and any size or auth constraints.

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?

Two tight sentences: the first front-loads the action, input format, and side effects; the second covers the return value. Both earn their place, with only mild redundancy between 'create a new project workspace' and the return sentence.

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 a three-parameter mutation tool with no annotations and no output schema, the description covers the essential picture: what goes in, what gets created, and what comes back. It would be fully complete with a note on behavior when the JSON is malformed or when the export references resources that already exist.

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 100%, so each of the three parameters is already documented in the schema, including the override semantics for name and description. The description adds only that the payload comes from export_project and contains collections, which is marginal beyond the schema. Baseline 3 is appropriate.

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 uses a specific verb ('Import') plus a precise resource ('portable project configuration JSON string previously produced by export_project') and enumerates the side effects — creating a project workspace and bulk-populating collections, mock endpoints, and conditional rules. That ties it clearly to export_project as its counterpart. It stops short of naming the closer siblings create_project and bulk_create_mocks, so an agent must infer the distinction rather than being told.

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

Usage Guidelines3/5

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

The phrase 'previously produced by export_project' implies the precondition for use — you have an exported payload in hand — which is useful implied routing. However, there is no explicit when-to-use versus create_project/bulk_create_mocks, and no when-not guidance (e.g., do not use for hand-built JSON or incremental additions).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources