SF Cleaning Service
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FROM_EMAIL | Yes | The email address to send from (e.g., gwen@irl-concierge.com) | |
| PARTNER_EMAILS | Yes | Comma-separated list of partner email addresses to notify | |
| RESEND_API_KEY | Yes | Your Resend API key for sending emails |
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 |
|---|---|
| request_cleaningC | Request cleaning service in San Francisco |
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 'request_cleaning' has a clear, distinct purpose that cannot be confused with any other tool in this set.
The naming pattern is trivially consistent since there is only one tool. The tool name 'request_cleaning' follows a clear verb_noun convention, and with no other tools to compare, there is no inconsistency.
A single tool is generally too few for a server's purpose, as it limits functionality and suggests an incomplete or thin surface. For a 'SF Cleaning Service' domain, one might expect additional tools for operations like scheduling, pricing, or status checks, making this count inappropriate for the apparent scope.
The tool set is severely incomplete for a cleaning service domain. While 'request_cleaning' covers initiation, there are obvious gaps such as checking service status, modifying or canceling requests, viewing pricing, or managing schedules. This will likely cause agent failures in handling full workflows.