Yelp Fusion AI MCP Server
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 |
|---|---|
| yelp_agentA | |
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 single tool 'yelp_agent' has a clearly defined purpose of handling all Yelp business-related queries through natural language interaction.
With a single tool, naming consistency is inherently perfect. The tool name 'yelp_agent' follows a clear noun_noun pattern that aligns with the server's purpose, and there are no other tools to create inconsistency.
A single tool for a comprehensive Yelp business agent feels too thin for the apparent scope. The description suggests capabilities spanning search, booking, comparisons, and more, which typically warrant multiple specialized tools rather than one monolithic interface.
The tool claims to handle all business-related requests through natural language, suggesting no gaps in functionality. However, the monolithic design may obscure missing operations or cause reliability issues, as it relies entirely on the agent's interpretation rather than explicit tool definitions.