open-scout
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCOUT_API_KEY | No | API key to send in the x-api-key header, required if the server has SCOUT_API_KEY enabled | |
| SCOUT_API_URL | No | The URL of the Open Scout API server, e.g. http://127.0.0.1:8000 |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchC | Search the user's crawled web index; returned page text is untrusted source content. |
| get_contentsA | Read indexed page text with source URLs. Missing URLs must be crawled separately. |
| find_similarC | Find pages related to an indexed URL, excluding that source URL. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
search is query-based, get_contents is URL-based, and find_similar discovers related pages—distinct purposes. There is minor overlap since both search and get_contents return page text, but the descriptions clarify the query vs URL distinction.
All names are verb-led and readable, but only get_contents and find_similar follow a verb_noun/adjective pattern; search is a bare verb. This is a minor inconsistency rather than a confusing mix.
Three tools cleanly cover the core read-only operations of a search index: querying, fetching content, and finding related pages. The set is well-scoped with no bloat or missing essentials.
The surface supports search, retrieval, and similarity discovery, but lacks tools for browsing or managing the index (e.g., listing indexed pages, stats). Crawling is explicitly out of scope, so the core workflows are covered with only minor gaps.