laya-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LAYA_MCP_MODEL | No | Hugging Face model ID or local directory for the Core ML model. | aac6fef/laya-multilingual-coreml-ane |
| LAYA_MCP_REVISION | No | Optional model revision. | |
| LAYA_MCP_LOG_LEVEL | No | Structured stderr log level. | INFO |
| LAYA_MCP_COMPUTE_UNITS | No | Compute units: 'all', 'cpu', 'cpu_gpu', or 'cpu_ne'. | model default |
| LAYA_MCP_LOCAL_FILES_ONLY | No | Set to 'true' to disable model downloads and lookups, requiring a cached or local model. | false |
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 |
|---|---|
| infoA | Report server, resident backend, model, platform, limits, and metrics. |
| decideA | Make one bounded decision using the resident local model. Decision kinds are |
| batch_decideA | Make ordered bounded decisions in one MCP request. Supply |
| filterB | Conservatively retain relevant, uncertain, failed, and oversized candidates. Only a sufficiently confident irrelevant result excludes a candidate. The
default response returns selected candidate text and aggregate metrics; use
|
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
decide and batch_decide are clearly the single-item and batch variants of the same operation, while filter is a distinct conservative retention workflow. An agent might briefly hesitate between filter and repeated decide calls for relevance tasks, but the descriptions make each tool's purpose specific enough to avoid serious ambiguity.
Most names are short, lowercase, action-oriented commands: info, decide, filter. batch_decide is the main deviation because it introduces an underscore and a compound form, but the naming remains readable and the relationship to decide is obvious.
Four tools is well-scoped for this server's purpose: server introspection, single decisions, batched decisions, and candidate filtering. Each tool covers a distinct core workflow without redundancy or unnecessary surface area.
The tool surface covers the full apparent workflow: checking server state and limits, making a single bounded decision, making batched decisions, and conservatively filtering candidates. Escalation is intentionally left to the caller, so there are no obvious dead ends or missing operations.