Skip to main content
Glama
Plenera MCP

Plenera MCP

Official
by Plenera-io

create_issues_from_spec

Create reviewed issue titles atomically from a spec, with backlinks and live embeds, and re-read after version conflicts to keep batches consistent.

Instructions

Atomically create reviewed issue titles with spec backlinks and live embeds. Re-read after version conflicts.

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>",
      "spec": "<spec>",
      "batch": "<batch>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "create_issues_from_spec"
  }
}

Input Schema

NameRequiredDescriptionDefault
specYes
batchYes
projectYes
idempotencyKeyYesStable key for this logical POST; reuse only with an identical body

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true. The description usefully adds atomic all-or-nothing semantics and a conflict-recovery instruction that annotations cannot express. It stops short of stating permissions required, what a partial failure looks like, or the direct consequences of the embedded backlinks.

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, front-loaded sentences with no filler; the operation and the concurrency caveat come first. 'Live embeds' is unexplained jargon, a minor clarity cost in an otherwise efficient definition.

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 nested-object, four-required-parameter batch mutation with no output schema and thin schema coverage, two sentences leave gaps: nothing on batch size limits, what is created per title, or whether the call is transactional across all titles and embeds. Adequate to attempt a call, insufficient to predict its edge behavior.

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 coverage is only 25% (only idempotencyKey is documented), so the description must compensate. It does clarify that spec is a backlink target and that batch.version acts as a concurrency token needing a re-read on conflict, but project, titles, and batch limits (max 20) are left entirely to the schema.

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?

States a specific verb and resource ('create ... issue titles') plus differentiating traits: atomic batch creation, spec backlinks, and live embeds. It is clearly not plain create_issue or create_spec, though it never names a sibling to route against.

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?

The only implied guidance is 'Re-read after version conflicts', which hints at optimistic-concurrency recovery but not when to pick this over create_issue, create_spec, or update_spec. No prerequisites, no exclusions, no preconditions such as whether the spec must already have a reviewed draft.

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