Skip to main content
Glama

CraftCI - Automated UX Craft & Billing-Safety CI Gate

craft_generate_ci_gate

Read-onlyIdempotent

Generate a ready-to-paste GitHub Actions workflow YAML and Markdown CraftCI gate configuration for a target minimum score.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "craft_generate_ci_gate"
  }
}

Input Schema

NameRequiredDescriptionDefault
minScoreNoMinimum Craft Score threshold (0-100)
previewUrlNoOptional staging preview URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the description does not contradict it. The description adds useful context by naming the exact output artifacts (YAML plus Markdown), but omits other behavioral detail an agent would want, such as what happens when minScore is omitted and whether the output is returned as text or written to disk.

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?

A single sentence that front-loads the verb and the deliverables, with no filler, hedging, or redundant restatement of the title. Every clause contributes information.

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 simple two-optional-parameter generator with no output schema, the description conveys the output shape well, which is the main thing an agent needs. It stops short of covering defaults (behavior with no minScore) and the role of previewUrl, leaving the agent to rely entirely on the schema for those.

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 both parameters (minScore, previewUrl) are already documented in the schema. The description only echoes the minScore concept via "target minimum score" and says nothing about how previewUrl alters the generated gate, so it adds little beyond the structured data. Baseline 3 applies when the schema carries the semantics.

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 concrete verb ("Generate") and two concrete artifacts (GitHub Actions workflow YAML and Markdown CraftCI gate configuration), plus the driving input (target minimum score). An agent can tell exactly what comes out. It does not distinguish itself from the siblings by name, but those siblings (audit snippet, posture report, billing safety) are clearly different operations, so the loss is minor.

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?

Usage is implied rather than stated: the phrase "ready-to-paste ... gate configuration" suggests this is for setting up CI gating in a repo, but there is no explicit when-to-use, when-not-to-use, or prerequisite (e.g., needs a Craft Score baseline first). No alternative tool is named or excluded.

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.