Skip to main content
Glama
Sign In
@illodev/taiga-mcp

@illodev/taiga-mcp

by illodev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

taiga_project_import

Import a project from a JSON dump to restore or replicate project data in Taiga.

Instructions

Import a project from a JSON dump.

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": {
      "dump": "<dump>"
    },
    "name": "taiga_project_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
dumpYesJSON string of the project export data

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states that it imports from a JSON dump but doesn't disclose whether it overwrites existing data, creates a new project, or what the side effects are. For a mutating operation, this is insufficient.

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 a single concise sentence with no redundant words. It front-loads the verb and resource clearly.

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?

This is a mutating import tool with no annotations and no output schema. The description doesn't explain the expected outcome, whether it creates a new project, or how to obtain the dump. It leaves important operational details unstated.

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?

The schema describes the single 'dump' parameter as 'JSON string of the project export data'. The description's 'JSON dump' adds no additional detail beyond the schema. With 100% schema coverage, baseline of 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 the specific verb 'Import' with the resource 'project' and specifies the source 'JSON dump', clearly distinguishing it from other project operations like create or list. However, it doesn't explicitly state whether this creates a new project or overwrites an existing one, so it loses the top score.

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?

No guidance on when to use this tool versus alternatives such as taiga_projects_create or taiga_project_export. The description merely states the action with no context on prerequisites 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

Other Tools