Horse Racing News
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_horse_racing_newsC | Fetch the latest horse racing news from Thoroughbred Daily News. Args: limit: Maximum number of stories to return (default: 10, max: 50) Returns: Dictionary containing feed information and list of news stories |
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 ambiguity or overlap between tools. The tool's purpose is clearly defined and singular.
Since there is only one tool, naming consistency is inherently perfect. The tool name follows a clear verb_noun pattern (get_horse_racing_news).
A single tool is too few for a news server, as it only supports fetching news without any filtering, searching, or categorization capabilities. This limits functionality and feels thin for the domain.
The server is severely incomplete for a news domain. It lacks essential operations such as searching news by keyword, filtering by date or category, or accessing specific articles, which are common in news APIs.