elastic / elastic/docs-content
[aw] Issue Scope Analyzer is missing required tool
- 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/29322779658
**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 documentation MCP server \(SemanticSearch, FindRelatedDocs\)**: The Elastic docs MCP server tools \(SemanticSearch, FindRelatedDocs\) are not available in this environment. Only GitHub, bash, file, and safeoutputs tools are accessible.
Alternatives:
| Tool | Alternative |
| --- | --- |
| Elastic documentation MCP server \(SemanticSearch, FindRelatedDocs\) | Run the Elastic docs MCP server locally or via a configured MCP client, then invoke SemanticSearch/FindRelatedDocs directly. Alternatively, search https://www.elastic.co/docs manually or use the Elastic search API. |
### 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/29322779658
````
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/29322779658`
> [!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/29322779658) · 52.1 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 21, 2026, 9:50 AM UTC
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with .github/workflows/gh-aw-docs-issue-scope.md and the failed run linked in the issue. Inspect how the Elastic documentation MCP server tools are configured and compare the workflow with pull request #5583. Done means the required tools are available and the Issue Scope Analyzer workflow completes without reporting them as missing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100