interdeep
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| extract_contentA | Extract clean text/markdown content from a URL using trafilatura (fast) with optional Playwright fallback (JS-rendered pages). |
| extract_batchB | Extract content from multiple URLs concurrently. Returns a list of extraction results. |
| compile_reportC | Compile research findings and sources into a structured markdown report with citations. |
| research_statusC | Show extraction capabilities and companion plugin readiness. |
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 4 tools
Each tool has a clearly distinct purpose with no ambiguity: compile_report creates reports from research, extract_batch handles multiple URLs concurrently, extract_content extracts from single URLs with fallback options, and research_status provides system status. The descriptions clearly differentiate their functions, making misselection unlikely.
All tools follow a consistent verb_noun pattern (compile_report, extract_batch, extract_content, research_status) with clear, descriptive names. There are no deviations in naming conventions, making the set predictable and easy to understand.
With 4 tools, the count is reasonable for a research/content extraction server, though slightly lean. Each tool earns its place by covering distinct aspects of the workflow, but the scope might benefit from additional tools for tasks like managing research sources or advanced report formatting.
The tool surface covers core research and extraction workflows well, including content extraction (single and batch), report compilation, and system status. Minor gaps exist, such as tools for editing reports, managing extracted data, or integrating with external research databases, but agents can work around these with the provided tools.