Skip to main content
Glama

Import project

import_project
Destructive

Import a base64 archive into the project

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_base64": "<data_base64>"
    },
    "name": "import_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNo
project_idNoProject id (or use session from use_project)
data_base64Yes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare the tool as destructive, non-idempotent, and open-world, but the description adds no behavioral context beyond the bare action. It does not explain overwrite semantics, whether an existing project is replaced, authentication requirements, size limits, or failure behavior.

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?

The description is a single front-loaded sentence with no filler or repetition. However, it is extremely terse for a destructive import operation with three parameters.

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?

For a destructive import tool with no output schema and incomplete parameter coverage, the description is too minimal. It leaves out critical operational details such as how project selection works, what format detection does, and what happens to existing project data.

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

Parameters2/5

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

Schema description coverage is only 33%. The description clarifies that data_base64 is a base64 archive, but it does not explain the format enum (tar.gz, zip, auto) or the project_id vs. session behavior beyond what the schema already states.

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 states a specific verb and resource: importing a base64 archive into a project. It is distinguishable from export_project by the action, but it does not explicitly differentiate itself from sibling tools or clarify scope.

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?

There is no guidance on when to use this tool versus alternatives such as export_project or use_project, nor are prerequisites or exclusions mentioned. The implied usage is only that it imports archives.

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