APLCart MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APLCART_USE_DB | No | Set to '1', 'true', or 'yes' to use SQLite database backend for faster searches instead of JSONL. | |
| OPENAI_API_KEY | Yes | Required for semantic search functionality using OpenAI embeddings. |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lookup-syntaxB | Return the record whose |
| searchB | Substring search across syntax, description and keywords (case-insensitive). |
| keywords-forC | Return the keyword list for the given |
| semantic-searchA | Natural language search using semantic embeddings. Use this for queries in everyday language when exact keywords might not match. |
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: keywords-for retrieves keyword lists for a syntax, lookup-syntax finds exact matches, search performs substring matching, and semantic-search handles natural language queries. There is no overlap in functionality, making tool selection straightforward for an agent.
The naming is mixed with hyphenated patterns (keywords-for, lookup-syntax) and single words (search, semantic-search). While readable, it lacks a consistent verb_noun convention, as keywords-for and lookup-syntax use hyphens and different verb styles, whereas search and semantic-search are more descriptive but not uniformly structured.
With 4 tools, the server is well-scoped for its apparent purpose of syntax and keyword lookup. Each tool serves a specific function in the domain, and the count is neither too sparse nor excessive, fitting typical expectations for a focused utility server.
The toolset covers core search and lookup operations effectively, including exact matching, substring search, and semantic search. A minor gap might be the lack of update or management tools if the domain includes mutable data, but for a query-focused server, the coverage is nearly complete.