mcp-agent-opt
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fullscope_contextA | Compressed file read for CONTEXT ONLY — strips comments, docstrings, types, and whitespace. Typical savings: 10-50% depending on comment density (up to 80% on heavily documented code, as low as 8% on minimal-comment code). Shows virtual line markers where content was stripped. NEVER use for files you plan to edit — comments and formatting are permanently removed from output. Use the built-in Read tool when you need to Edit a file. |
| fullscope_skeletonA | Ultra-compressed file read showing ONLY function/class/method signatures with IMPORTS and EXPORTS summary — all implementation bodies are replaced with expand handles. Strong on function-heavy code (80-99% savings), weaker on flat data/config files. Use when you need to understand a module API surface without reading implementation details. NEVER use for files you plan to edit. For implementation details, use fullscope_context. For editing, use the built-in Read tool. |
| fullscope_expandA | Drill into a specific function from a fullscope_skeleton output. Takes a file path + expand handle (e.g. "fn:login" from the skeleton placeholder). Returns just that function body with context-level compression (comments stripped, logic preserved). Use this to progressively disclose detail: start with fullscope_skeleton (cheapest), then fullscope_expand only for functions you care about. |
| fullscope_searchA | Search files with compressed results — runs ripgrep and filters output through fullscope to save tokens. Use instead of Grep/Bash for exploratory searches where you need to scan many results. For precise searches where you need exact line content, use the built-in Grep tool. |
| fullscope_usagesA | Find where a symbol (function, class, variable) is imported or referenced across the project. Returns results grouped by file. Complements fullscope_skeleton — skeleton shows what a file provides, usages shows where those exports are consumed. Best for: debugging "who calls this?", understanding dependencies. |
| fullscope_batch_contextA | Read multiple files in one call, each minified. Saves tool-call overhead. Supports: (1) intent parameter — tell the tool WHY you're reading these files and it biases minification to preserve relevant content; (2) token budgeting — files auto-downshift from context to skeleton using information density; (3) cross-file import dedup; (4) dependency-ordered output (leaf deps first as skeleton, importers after with full context). |
| fullscope_projectA | Compressed codebase orientation — returns filtered directory tree, key config files (package.json/Cargo.toml/etc compressed), git status, and detected entry points with their critical-path dependencies. Use this as the first call when exploring a new codebase. |
| fullscope_verify_lineA | Verify a line number from a compressed view against the raw file. Since compressed output preserves original line numbers via virtual markers, this confirms the line content matches. Returns the raw line with ±5 lines of context. Optionally pass expected_content to verify the match. Use before editing to confirm the exact location. |
| fullscope_statsA | Show session savings: total files compressed, tokens saved, estimated cost savings, and context-rot warnings for files read too many times. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/justguy/FullScope-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server