Satori Syntax 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 |
|---|---|
| generate_satori_syntaxC | さとり構文を生成します（140文字のX投稿用） |
| get_satori_structure_typesB | さとり構文の利用可能な構文タイプ一覧を取得します |
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 have completely distinct purposes: one generates content (generate_satori_syntax) and the other retrieves metadata about available structure types (get_satori_structure_types). There is no overlap in functionality, making it impossible for an agent to confuse them.
Both tools follow a consistent verb_noun naming pattern (generate_satori_syntax, get_satori_structure_types) with clear, descriptive verbs that match their actions. The naming is uniform and predictable across the set.
With only 2 tools, the server feels thin for its purpose of generating and managing Satori syntax. A typical syntax generation server might include additional tools for validation, customization, or history management, making this set borderline minimal.
The server covers core generation and type listing, but there are notable gaps. For example, no tools exist for validating syntax, editing generated content, or managing user preferences, which could limit agent workflows in this domain.