dayi-search-mcp
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dayi_queryD | – |
| dayi_query_autoD | – |
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 2 tools
Both tools have no descriptions and nearly identical names (dayi_query vs dayi_query_auto), making them indistinguishable for an agent.
Names follow a consistent prefix 'dayi_query' but one has a suffix '_auto', creating ambiguity. The pattern is present but unclear.
Only two tools are provided for a search service, which likely requires more operations like filtering, pagination, or results management.
Without descriptions, it's unclear what the tools do, but having only two query-like tools suggests significant gaps in search functionality.