elastic / elastic/docs-content

[aw] Issue Scope Analyzer is missing required tool

Open
#7,221 0 comments 0 reactions 0 assignees View on GitHub
agentic-workflows
Dominant language
No language data
Stars
47
Forks
261
Avg merge
3d 21h
Merged PRs (30d)
141

Description

### Workflow Failure

**Workflow:** [Issue Scope Analyzer](https://github.com/elastic/docs-content/blob/main/.github/workflows/gh-aw-docs-issue-scope.md)
**Branch:** main
**Run:** https://github.com/elastic/docs-content/actions/runs/28786794169
**Pull Request:** [#5583](https://github.com/elastic/docs-content/pull/5583)

> [!WARNING]
> **Missing Tools Reported**: The agent reported missing tools during execution.

**Missing Tools:**
- **elastic-docs MCP server \(SemanticSearch, FindRelatedDocs, GetDocumentByUrl\)**: The elastic-docs MCP server tools are not available in this environment. Available tools are bash, grep, glob, GitHub tools, and safeoutputs tools only.

Alternatives:

| Tool | Alternative |
| --- | --- |
| elastic-docs MCP server \(SemanticSearch, FindRelatedDocs, GetDocumentByUrl\) | I can search the docs-content repository directly using grep/glob to find relevant documentation files for Elastic Defend, CCS, response actions, and Fleet remote output. |

### Action Required

**Assign this issue to an agent** to debug and fix the issue.

Debug with any coding agent

Use this prompt with any coding agent (GitHub Copilot, Claude, Gemini, etc.):

````
Debug the agentic workflow failure using https://raw.githubusercontent.com/github/gh-aw/main/debug.md

The failed workflow run is at https://github.com/elastic/docs-content/actions/runs/28786794169
````

Manually invoke the agent

Debug this workflow failure using your favorite Agent CLI and the `agentic-workflows` prompt.

- Start your agent
- Load the `agentic-workflows` skill from `.github/skills/agentic-workflows/SKILL.md` or
- Type `debug the agentic workflow gh-aw-docs-issue-scope failure in https://github.com/elastic/docs-content/actions/runs/28786794169`

> [!TIP]
>
> Stop reporting this workflow as a failure
>
> To stop a workflow from creating failure issues, set `report-failure-as-issue: false` in its frontmatter:
> ```yaml
> safe-outputs:
> report-failure-as-issue: false
> ```
>
>

> Generated from [Issue Scope Analyzer](https://github.com/elastic/docs-content/actions/runs/28786794169) · 164.8 AIC · [◷](https://github.com/search?q=repo%3Aelastic%2Fdocs-content+is%3Aissue+%22gh-aw-workflow-id%3A+gh-aw-docs-issue-scope%22&type=issues)
> - [x] expires on Jul 13, 2026, 11:13 AM UTC

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with .github/workflows/gh-aw-docs-issue-scope.md and inspect the failed run linked in the issue, then compare its available tools with the required elastic-docs MCP server tools. Trace the workflow configuration and agentic-workflows guidance to identify why the server is unavailable. Done means the workflow can access SemanticSearch, FindRelatedDocs, and GetDocumentByUrl during execution without reporting missing tools.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.