sett-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.
Read and manage contacts. Write tools only appear when writes are enabled.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| acme_search_contactsA | Find contacts whose name, company or any other field contains the query (case-insensitive). Use this first when you don't know a contact's id. Each result includes the id to pass to the other contact tools. Masked fields show as "[masked]". |
| acme_get_contactA | Get every field of one contact by its id. Use this when you already have an id, for example from search results. If you only know a name or company, use search instead. |
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
The two tools are cleanly separated: search by fuzzy field match versus get by exact id. Descriptions explicitly tell the agent which to use and reference each other, leaving no realistic chance of misselection.
Both names follow the same `acme_verb_noun` convention, which is predictable. The only nit is `search_contacts` (plural) versus `get_contact` (singular), a minor deviation that does not hinder readability.
Two tools is thin for a contact-management surface, though it is plausible for a deliberately read-only gateway. It sits at the borderline where the surface feels minimal rather than well-scoped.
The surface covers only read access: search and retrieve by id. There is no way to create, update, delete, or enumerate contacts, so any write workflow or bulk listing is a dead end.