@ktmcp/betfair
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| post__requestD | This is a socket protocol delimited by CRLF (not http) |
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
Only one tool exists, so there is no possibility of confusing it with another tool. The tool set has zero ambiguity in terms of tool selection.
With a single tool, naming consistency is trivially maintained. However, the name 'post__request' is unconventional and not a clear verb_noun pattern, making it somewhat unpredictable.
A single trivial tool for what appears to be a Betfair server is an extreme mismatch. The tool does not cover the expected scope of a betting exchange API.
The server provides no apparent functionality for Betfair operations such as market data, betting, or account management. The one tool is a low-level socket request, leaving the domain severely incomplete.