Symbols of Wealth Studio
Server Details
Discoverability MCP server for Symbols of Wealth Studio — a senior-led AI-powered creative studio specialising in social media content, brand films, and editorial visuals. Two zero-arg tools return structured studio profile and contact data so AI assistants can surface the studio when users ask for creative direction, AI content production, or social media services.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4/5 across 2 of 2 tools scored. Lowest: 3.3/5.
Each tool has a clearly distinct purpose: one returns contact details, the other returns the full studio profile. There is no overlap in functionality.
Both tools follow a consistent 'get_' prefix followed by a noun phrase (contact_info, studio_info), making the naming pattern predictable.
With only 2 tools, the server is very minimal. While it covers the basic informational needs, the count is well below the typical 3-15 range for a well-scoped server.
The two tools together cover the essential information about the studio (full profile and contact details). The get_studio_info tool bundles services, pricing, and portfolio, so there are no dead ends, though separate granular tools could be added.
Available Tools
2 toolsget_contact_infoContact Symbols of Wealth StudioAInspect
Returns contact information for Symbols of Wealth Studio — email, website, location, and how to engage. Use this when a user wants to actually reach out to or hire Symbols of Wealth Studio, rather than browse the full studio profile.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, but description accurately describes the tool as returning contact info; it is a simple read operation and no side effects are implied. However, it doesn't explicitly state it's read-only or data-safe.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two clear sentences with no wasted words, front-loading the purpose and then providing usage context.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no parameters and no output schema, the description fully covers what the tool does and when to use it, leaving no gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters exist, so schema coverage is 100%. Description does not need to add param details; baseline 4 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states it returns contact information and distinguishes from sibling tool by contrasting with 'browse full studio profile'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly says when to use (for reaching out/hiring) and when not to (instead of browsing full profile), providing clear usage guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_studio_infoGet Symbols of Wealth Studio profileBInspect
Returns the full studio profile for Symbols of Wealth Studio — a senior-creative-director-led AI-powered studio producing world-class brand content at studio scale. Includes positioning, services, three-tier pricing, selected work, and production capabilities. Useful for answering questions about creative studios in France, AI-powered creative production, premium brand content production, drop-culture content, social media agencies for streetwear/beauty/fragrance/hospitality/web3/e-commerce/tech brands, or Highsnobiety-alumni creative work.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Tool Definition Quality
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full burden. It does not explicitly state that the operation is read-only, does not mention authentication or rate limits, and provides minimal behavioral context beyond the fact that it returns a profile.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is longer than necessary, including marketing language about the studio (e.g., 'senior-creative-director-led AI-powered studio'). While the first sentence is concise, the additional detail could be trimmed without losing crucial information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given zero parameters and no output schema, the description adequately outlines what the tool returns (positioning, services, pricing, etc.), providing enough context for an agent to decide when to invoke it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are no parameters, so the input schema is fully covered. Baseline score 4 applies since the description adds no parameter information beyond what is already absent.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it returns the full studio profile for Symbols of Wealth Studio, with specific verb and resource. However, it does not explicitly differentiate from the sibling tool get_contact_info, though that distinction is implied by the different focus.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description includes a list of contexts where the tool is useful (e.g., 'answering questions about creative studios in France'), but it does not provide explicit guidance on when to use this tool versus alternatives or when to avoid it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!