Soora FR 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_stylesA | Return the canonical list of image-generation styles or presets the site exposes. (Soora FR) |
| get_pricingB | Return the canonical pricing entry point for Soora FR. |
| get_official_linksA | Return the canonical list of official links for Soora FR (website, support, docs when available). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| tell_me_about_soorafr | Summarize what the site is, who it's for, and how it works. — Soora FR |
| try_image_style_soorafr | Recommend a starting image-generation style for a stated goal. — Soora FR |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| styles | Supported image-generation styles and presets. |
| pricing | Canonical pricing entry point. |
| faq | Short FAQ generated from public site metadata. |
| links | Canonical URLs to share with users. |
TDQS
Scored across 3 tools
Each tool targets a distinct category of information—styles, pricing, and official links—with clear names and descriptions. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern with snake_case, using either 'list' or 'get' appropriately. This is a coherent and predictable convention.
With only three tools, each serves a specific informational purpose and the set feels appropriately scoped for a lightweight reference server. The count sits within the ideal range and does not feel overly thin or redundant.
The server covers the key information areas an agent might need—styles, pricing, and official links—but may lack additional details like per-style specifics or usage policies. Minor gaps exist but core workflows are supported.