Argus
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ARGUS_AUTHORITY_URL | Yes | URL of your Argus HTTP authority. Must be reachable from the MCP adapter. | |
| ARGUS_AUTHORITY_TOKEN | Yes | Scoped bearer token issued by your Argus HTTP authority. Do not supply provider keys or database configuration. |
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 |
|---|---|
| search_webC | Search through the authenticated Argus HTTP authority. |
| recover_urlC | Recover a dead or moved URL through HTTP. |
| expand_linksC | Expand related links through HTTP. |
| extract_contentC | Extract content through the authenticated HTTP authority. |
| search_healthA | Read provider health from the HTTP authority. |
| search_budgetsB | Read durable provider budgets from the HTTP authority. |
| search_web_v2D | Search through the HTTP-v2 evidence authority. |
| recover_url_v2D | Recover a URL through the HTTP-v2 evidence authority. |
| expand_links_v2C | Expand related links through the HTTP-v2 evidence authority. |
| extract_content_v2D | Extract content through the HTTP-v2 evidence authority. |
| recover_dead_articleD | – |
| capture_siteD | – |
| build_research_packD | – |
| get_workflow_statusC | Read safe research-pack status from the authenticated authority. |
| read_workflow_artifactC | Read a bounded report or manifest slice from the authority. |
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 15 tools
Four tool pairs are near-duplicates distinguished only by references to a 'HTTP' vs 'HTTP-v2 evidence' authority (search_web/search_web_v2, recover_url/recover_url_v2, expand_links/expand_links_v2, extract_content/extract_content_v2), giving an agent no clear basis for choosing. Additionally, recover_url and recover_dead_article overlap, and capture_site/build_research_pack have no descriptions at all, leaving their boundaries undefined.
Names consistently follow snake_case verb_noun (search_web, expand_links, get_workflow_status, read_workflow_artifact). The only deviation is the _v2 suffix convention, which is at least applied uniformly but signals duplication rather than a distinct capability.
15 tools sits at the upper edge of a comfortable set, and roughly half of it is duplicated v1/v2 surface, so the effective unique capability count is closer to 11. The count feels inflated for the actual scope of a web-research pipeline.
The surface covers a plausible research lifecycle — search, recover, expand, extract, capture, build a research pack, and poll/read workflow output plus health and budgets. However there are no cancellation/cleanup operations for workflows or packs, and two tools (capture_site, build_research_pack) lack descriptions, making their role and coverage impossible to verify.