advisorsai-check (Advisors AI)
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| advisors_public_page_basics_checkA | On explicit request, fetch one credential-free public HTTP(S) page and its same-origin robots.txt, sitemap.xml and llms.txt. Return the library's signals, completeness, coverage and score (null if incomplete). Private networks and non-standard web ports are rejected by the checker. No API key, HMAC receipt, ranking or answer-engine visibility measurement is provided. |
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 1 tool
Only one tool exists, so there is no possibility of confusing it with another. Its purpose—fetching a single public page plus robots.txt/sitemap.xml/llms.txt and scoring library signals—is explicitly stated.
The single name is descriptive snake_case with a namespace prefix (advisors_) and a clear action suffix (check), which is readable and predictable. With only one tool there is no pattern to verify, so it falls just short of a 5.
For a narrowly scoped public-page audit checker, a single tool is defensible and each capability is bundled coherently. It is still on the thin side (1 tool), leaving no room for complementary operations.
It covers the stated single-page fetch-and-score workflow including robots/sitemap/llms retrieval, but the surface is a dead end: no batch checks, no multi-page crawl, no history or comparison, and no follow-up actions. Agents needing anything beyond one page check will be blocked.