Skip to main content
Glama
powmarx

pow-mcp-rag-new

by powmarx

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_docsA

Semantic search across indexed project documentation.

Args: query: Natural language search query (e.g., "how does dispense rejection work") project: Optional project name to filter results. Leave empty to search all projects. top_k: Number of results to return (default: 5, max: 20) file_type: Optional filter by file type: "header", "source", "documentation", "config"

Returns: Relevant document chunks with metadata (file path, project, type)

search_specsA

Search only specification and documentation files (filters out source code). Use when you need "what does the spec say about X" without code noise.

Args: query: Natural language search query project: Optional project name filter top_k: Number of results (default: 5, max: 20)

Returns: Relevant documentation chunks (specs, requirements, design docs, PDFs)

search_codeA

Search only source code and header files (filters out documentation). Use when you need implementation details.

Args: query: Natural language search query project: Optional project name filter top_k: Number of results (default: 5, max: 20) headers_only: If true, search only header files (API contracts)

Returns: Relevant source code chunks

search_hex_patternA

Search for hex error codes or patterns in indexed documents using text matching. Supports partial matches (e.g., '88a153' finds 88a15300, 88a15310, etc.) Use this for device error codes, packet IDs, or any hex value lookup.

Args: pattern: Hex pattern to search for (e.g., "88a153", "0x0521", "ERROR_118") project: Optional project name to filter results. Leave empty to search all. top_k: Maximum results to return (default: 10)

Returns: Document chunks containing the hex pattern with file and project info

find_variableB

Find where a specific variable, constant, enum value, or #define is defined and used. Uses text matching to find exact occurrences across indexed files.

Args: variable_name: Name of the variable/constant to find project: Optional project name filter

Returns: Files containing the variable with context snippets

find_functionA

Find where a function is defined (headers) and used (source files).

Args: function_name: Name of the function to find (e.g., "StoreMoney", "CmdDispense") project: Optional project name filter

Returns: Header declarations and source usages of the function

get_documentA

Retrieve all indexed chunks of a specific document.

Args: file_path: Relative file path within the project (e.g., "src/Device.h") project: Project name (e.g., "my-project")

Returns: Full reconstructed document content from indexed chunks

list_projectsA

List all indexed projects and their statistics.

Returns: List of projects with document counts and descriptions

list_filesA

List all indexed files for a project, optionally filtered by type.

Args: project: Project name (e.g., "my-project") file_type: Optional filter: "header", "source", "documentation", "config"

Returns: List of indexed file paths with their types

get_project_summaryA

Get a quick overview of an indexed project: description, file counts by type, total chunks.

Args: project: Project name

Returns: Project summary with statistics

compare_projectsA

Search for the same concept in two projects side by side. Useful for comparing implementations across two versions or variants of the same project.

Args: query: What to search for (e.g., "dispense command flow") project_a: First project name project_b: Second project name top_k: Results per project (default: 3)

Returns: Side-by-side results from both projects

add_projectA

Add a new project to the RAG index. Auto-detects source patterns and indexes immediately.

Args: name: Unique project name (e.g., "my-new-api") path: Absolute path to the project root directory

Returns: Summary of detected patterns and indexing result

add_fileA

Index a specific file into an existing project and persist it in config.yaml so it gets re-indexed automatically on future runs.

Args: file_path: Absolute path to the file to index project: Project name to add the file to (must already exist)

Returns: Confirmation with chunk count, or error message

add_folderA

Index all files in a folder into an existing project and persist the pattern in config.yaml so the folder gets re-indexed automatically on future runs.

Args: folder_path: Absolute path to the folder to index project: Project name to add the folder to (must already exist) pattern: Glob pattern for files within the folder (default: "**/*" for all files)

Returns: Confirmation with file/chunk counts, or error message

add_patternA

Add a glob pattern to an existing project and index matching files immediately. Persists the pattern in config.yaml so it gets re-indexed automatically on future runs.

Use this when you want to index a specific set of files by pattern rather than pointing at a concrete folder path. The pattern is relative to the project base_path.

Args: project: Project name to add the pattern to (must already exist) pattern: Glob pattern relative to project base_path (e.g., "doc/specifications/**/*.md") type: File type classification — one of: source, header, documentation, config (default: documentation) description: Optional human-readable description for this source entry

Returns: Confirmation with file/chunk counts, or error message

Examples: add_pattern("my-project", "doc/specifications//*.md", "documentation", "Hardware specs") add_pattern("my-project", "src//*.json", "config", "JSON config files")

remove_projectA

Remove a project from the RAG index. Deletes all indexed chunks and marks the project as removed in config.yaml (preserving configuration for future re-add).

Args: name: Project name to remove (e.g., "my_device_logs")

Returns: Confirmation of removal with chunk count deleted.

clear_project_indexA

Clear all indexed data for a project without removing it from config.yaml. The project remains configured and can be re-indexed later.

Args: name: Project name to clear (e.g., "my_device_logs")

Returns: Confirmation with number of chunks deleted.

remove_file_from_indexA

Remove all indexed chunks for a specific file from a project's index. Useful for removing large log files or outdated files without clearing the entire project.

Args: file_path: Relative file path within the project (e.g., "device-26-04-28.log") project: Project name (e.g., "my_device_logs")

Returns: Confirmation with number of chunks removed.

search_logsA

Search indexed log events with structured filtering and semantic search.

Args: query: Semantic search query (max 512 chars). Optional if filters provided. project: Filter by project name. severity: Filter by severity (DEBUG, INFO, WARNING, ERROR, CRITICAL). time_range_start: ISO 8601 start time filter. time_range_end: ISO 8601 end time filter. error_code_pattern: Prefix match on error codes (e.g., "88a1"). device_id: Filter by device identifier. event_type: Filter by event type (command, response, error, etc.). top_k: Max results (default 20, max 50). Clamped to range [1, 50].

Returns: Formatted results with metadata and relevance scores.

index_log_fileA

Index a specific log file (or time window within it) on demand. Use this instead of waiting for background reindex on large log files.

Args: file: Log filename or glob pattern (e.g., "device-26-04-28.log", "device-2026-05-14*.log") project: Project name containing log sources (required) time_from: Optional start time filter, HH:MM:SS format (e.g., "14:00:00"). Only index events at or after this time. time_to: Optional end time filter, HH:MM:SS format (e.g., "15:30:00"). Only index events at or before this time.

Returns: Summary of indexing results (files processed, chunks created, time range)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

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/powmarx/pow-mcp-rag-new'

If you have feedback or need assistance with the MCP directory API, please join our Discord server