Skip to main content
Glama
Sign In
kiro-frontend-engineer-mcp

kiro-frontend-engineer-mcp

by Josephjyinn516
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

github_fetch_ci_logs

Retrieve CI build and lint failure logs from GitHub Actions to enable automated self-healing and fix generation.

Instructions

Fetch CI build/lint failure logs from GitHub Actions. Used for self-healing: agent reads failures and generates fixes.

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": {
      "owner": "<owner>",
      "repo": "<repo>",
      "runId": "<runId>"
    },
    "name": "github_fetch_ci_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
ownerYesGitHub repository owner
repoYesGitHub repository name
runIdYesGitHub Actions workflow run ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description must disclose behaviors. It implies a read-only fetch but omits details like permissions, rate limits, or handling of missing logs.

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?

Two sentences, no unnecessary words. Front-loaded with action, then states purpose. Highly concise.

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?

Given three required parameters and no output schema, the description adequately covers purpose and usage. Could mention return format (e.g., raw logs) or limitations for full completeness.

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 100%, so the schema already describes all three parameters. The description adds no additional meaning beyond 'owner', 'repo', and 'runId'.

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?

The verb 'Fetch' and resource 'CI build/lint failure logs from GitHub Actions' are specific. The self-healing use case distinguishes it from unrelated siblings.

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?

It explicitly states the use case 'Used for self-healing: agent reads failures and generates fixes', providing clear context but no when-not-to-use or alternatives.

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