laya-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LAYA_MODEL | No | Pin "english", "multilingual" or "typed-decisions" to avoid checkpoint reloads. | auto-router per request |
| LAYA_DEVICE | No | Force "cpu" if VRAM is tight. | auto (cuda if available, else cpu) |
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 |
|---|---|
| decideB | Make typed decisions about a state. questions maps an id to {type: "choice"|"score"|"noul", instructions, criteria}. For choice, criteria is {key: description}; for score, a list of level labels. Returns each answer with a probability distribution. |
| classifyA | Pick the single best label for a text, with calibrated confidence and a score for every label. Use for routing, tagging, moderation, triage. |
| scoreB | Rate a text on an ordered scale given by criteria (low to high). Returns the probability-weighted score plus the distribution. |
| checkB | Answer a yes/no question about a state. Returns P(yes) in [0,1]. |
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 is a generic decision engine that can handle choice and score types, which substantially overlaps with classify and score. The specialized tools add context (text vs. state), but the boundaries are not crisp, and an agent could easily misselect decide for tasks the others are designed for.
All four tool names are single lowercase verbs with no mixed conventions or inconsistent patterns. The imperative style is consistent and easy to predict, even if the verbs are somewhat generic.
Four tools is a reasonable number for a decision/classification/rating server. However, decide's broad scope makes classify, score, and check feel somewhat redundant, so the count earns slightly less than full marks.
The set covers common decision tasks: choice/classification, ordered scoring, and yes/no checking, plus the generic noul type through decide. Minor gaps exist around batch processing or clearer support for unstructured outputs, but the core decision surface appears well covered.