FullScope-MCP
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| call_modelC | |
| scrape_webpageC | |
| summarize_contentB | |
| summarize_webpageB | |
| read_and_summarize_text_fileC | |
| read_and_summarize_pdf_fileB | |
| topic_based_summaryB | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_server_config | 获取服务器配置信息 |
TDQS
Scored across 7 tools
There is significant overlap between tools, particularly the summarization functions: read_and_summarize_pdf_file, read_and_summarize_text_file, summarize_content, summarize_webpage, and topic_based_summary all perform summarization with similar parameters. However, their descriptions clarify different input sources (PDF, text file, arbitrary content, webpage, topic-based), which helps reduce complete confusion but still creates ambiguity about when to use which tool.
Most tools follow a consistent verb_noun pattern (e.g., read_and_summarize_pdf_file, scrape_webpage, summarize_content), with clear action-object naming. The only minor deviation is 'call_model' which uses a simpler verb_noun style, but overall the naming is predictable and readable across the set.
With 7 tools, this is a well-scoped set for a content processing and summarization server. Each tool appears to serve a specific purpose within the domain, and the count is neither too thin nor overwhelming, fitting typical server scopes of 3-15 tools effectively.
The tool set covers core content processing workflows: model calling, file reading (PDF and text), web scraping, and multiple summarization methods. Minor gaps exist, such as no explicit update or delete operations for processed content, but agents can likely work around this given the server's focus on summarization and information extraction rather than content management.