Skip to main content
Glama

ecosystem_start_integration

Builds a ready-to-POST task_create payload from a completed deep review, adds a lifecycle:integrated tag, and advances stage_status so you can hand implementation to the existing task system.

Instructions

Stage 3 integrate path — build a task_create payload + tag the repo.

Adds lifecycle:integrated tag, advances stage_status, and returns a task payload (title / description / priority / horizon / tags) ready to POST to /api/projects/{project_id}/tasks. After the task is created, call ecosystem_link_integration_task to write integration_task_id back onto the review.

The ecosystem does not take over implementation — task ownership is taken over by the existing task/team system.

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": {
      "deep_review_id": "<deep_review_id>"
    },
    "name": "ecosystem_start_integration"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoOptional task title (auto-generated if empty).
horizonNoTask horizon — short / mid (default) / long.mid
priorityNoTask priority — critical / high (default) / medium / low.high
extra_tagsNoAdditional tags appended to the task.
descriptionNoOptional task description (auto-generated if empty).
deep_review_idYesTarget deep_review row id (must be debated / architecture_done / referenced).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.11.2

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose non-obvious side effects: it adds a lifecycle:integrated tag, advances stage_status, and does not itself create the task. Missing are idempotency behavior, permission/auth requirements, and what happens if the row is already integrated.

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?

Front-loaded with the stage and the concrete action, followed by effects, then next step, then scope caveat—a sensible order. The prose is slightly loose and heavy on backticks, but every sentence carries information.

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 six-parameter mutation tool with no annotations but a rich output schema, the description covers sequencing, side effects, and ownership boundaries well; since an output schema exists, it needn't explain return values. Preconditions and failure modes (e.g., what happens on a review not yet at stage 3) are left to the schema.

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 the baseline is 3. The description does add one useful link: the input fields correspond to the returned task payload fields, and the payload is 'ready to POST' to /api/projects/{project_id}/tasks. It does not add format or constraint detail beyond the schema.

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?

Names a specific verb and artifact ('build a task_create payload + tag the repo') and places it precisely at 'Stage 3 integrate path'. It implicitly separates itself from task_create (it builds a payload, it does not create the task) and from ecosystem_link_integration_task (the follow-up step), so an agent can place it in the pipeline without opening the schema.

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?

Gives sequencing guidance that is genuinely actionable: call this, POST the returned payload, then call ecosystem_link_integration_task to write integration_task_id back. It also sets a scope boundary ('the ecosystem does not take over implementation'). It does not state when to avoid this tool or what to do if the review isn't yet at stage 3, which keeps it short of a 5.

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