DocsScraper
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOCS_SCRAPER_API_KEY | Yes | API key for authentication |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_docsB | Search through documentation chunks using semantic search. Make sure your query is specific to get the best results. Forgetting to add 'api' to the query will return ui results etc. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| DocsScraper API Info | Information about the connected DocsScraper API |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'search_docs' has a single, clear purpose of searching documentation chunks using semantic search, so agents cannot misselect among multiple options.
The naming follows a consistent verb_noun pattern with 'search_docs', and since there is only one tool, there are no deviations or mixed conventions to evaluate. The naming is straightforward and predictable.
A single tool for a server named 'DocsScraper' feels too thin for the apparent scope, as scraping documentation typically involves more operations like fetching, parsing, or updating content. One tool may limit functionality and agent workflows, making it borderline inadequate.
The tool surface is severely incomplete for a documentation scraping domain. While 'search_docs' provides search capability, there are obvious gaps such as no tools for retrieving, listing, or managing documentation sources, which are essential for comprehensive scraping operations.