snw-derived-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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| snw_list_object_typesA | 列出可作为派生字段根对象的对象类型。 |
| snw_get_object_neighborhoodA | 返回对象在最多三跳内的全部无环 Link 路径及每跳基数。 |
| snw_analyze_field_requestC | 在三跳邻域内解析字段来源、校验基数，并生成不可变语义计划和 SQL。 |
| snw_create_derived_propertyB | 持久化只读派生属性；同名替换必须显式设置 replace_existing。 |
| snw_execute_derived_propertyC | 在本地 Amazon Ads mock 数据上执行已注册派生属性。 |
| snw_list_derived_propertiesA | 列出已创建派生属性及完整可审计语义计划。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| snw_define_derived_property |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| snw_ontology_schema | |
| snw_derived_registry |
TDQS
Scored across 6 tools
Each tool targets a distinct resource or action: object type enumeration, graph neighborhood exploration, execution, analysis/planning, creation, and listing. There is no meaningful overlap that would cause an agent to confuse one tool with another.
All tools share a consistent snw_ prefix and follow a clear verb_noun pattern. The minor singular/plural variation (derived_property vs derived_properties) is standard and does not create confusion.
Six tools is well-scoped for the derived-property workflow. Each tool covers a distinct step in the lifecycle without unnecessary redundancy or bloat.
The server covers exploration, analysis, execution, creation/replacement, and listing of derived properties. The only notable gap is the lack of an explicit delete/drop operation, though replace_existing covers updates and the core workflow is otherwise complete.