oh-my-laya
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
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 |
|---|---|
| laya_tell_meB | Run a local typed decision with Laya-MLX. Use for bounded classification, ordered scoring, and yes/no probability. Question types are choice, score, and noul. Treat results as advisory; never use them as authorization for destructive or consequential actions. |
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 1 tool
With only one tool, there is no possibility of confusing it with another. The tool's purpose is clearly distinct by default.
The name 'laya_tell_me' is readable and uses a consistent imperative style with a product prefix. Since there is only one tool, there is no conflicting naming convention to penalize heavily.
A single tool feels quite thin for a server, even if the intended scope is narrow. It is borderline and could benefit from at least one supporting tool, such as model inspection or configuration.
The tool appears to cover the advertised decision types: choice, score, and yes/no probability. Minor gaps like model management or detailed output explanations exist, but the core decision workflow is functional.