NewsDigest 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 |
|---|---|
| list_toolsA | List all available MCP tools with descriptions and categories |
| move_fileB | Move a TypeScript/JavaScript file to a new location and update all import statements |
| move_directoryA | Move a directory to a new location, updating all TypeScript imports and references automatically |
| rename_symbolB | Rename a TypeScript symbol (variable, function, class, etc.) across the codebase |
| delete_symbolB | Delete a TypeScript/JavaScript symbol (variable, function, class, etc.) and all its references |
| get_module_symbolsC | Get all exported symbols from a TypeScript/JavaScript module without detailed signatures |
| get_type_in_moduleC | Get detailed signature information for a specific type (function, class, interface, type alias, etc.) from a module |
| get_type_at_symbolC | Get type information for a TypeScript/JavaScript symbol at a specific location |
| get_symbols_in_scopeA | Get all symbols (variables, types, functions, etc.) visible at a specific location in a TypeScript/JavaScript file |
| find_referencesC | Find all references to a TypeScript/JavaScript symbol across the codebase |
| get_definitionsC | Get the definition(s) of a TypeScript symbol |
| get_diagnosticsB | Get TypeScript diagnostics (errors, warnings) for a single file |
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 12 tools
Most tools have distinct purposes targeting specific TypeScript/JavaScript code analysis tasks, but there is some overlap between get_definitions and get_type_at_symbol that could cause confusion. Tools like find_references and rename_symbol are clearly differentiated by their action scope.
All tools follow a consistent verb_noun naming pattern with clear, descriptive names. The naming convention is uniform throughout, using snake_case consistently without any deviations or mixed styles.
12 tools is well-scoped for a TypeScript/JavaScript code analysis server, covering a comprehensive range of operations from diagnostics to refactoring. Each tool appears to serve a specific, justified purpose within the domain.
The toolset provides strong coverage for code analysis, refactoring, and diagnostics, but lacks tools for creating or modifying code (e.g., add_symbol, update_file). This minor gap could limit agents in full development workflows, though core analysis tasks are well-covered.