World-class creative social media content studio, powered by AI.
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.
Average 4.6/5 across 2 of 2 tools scored.
The two tools are mostly distinct: get_studio_info returns the full profile, while get_contact_info focuses on contact details. Some overlap exists since contact info is part of the profile, but the descriptions clearly differentiate the use cases.
Both tool names follow a consistent get_verb_noun pattern, which is predictable and easy for an agent to understand.
With only 2 tools, the server is on the thin side, but for a simple studio info lookup purpose, it is acceptable. The tools are well-scoped and each serves a clear need.
The domain is studio information, and the two tools cover the main needs: getting the full profile and getting contact details. Minor gaps like separate service or pricing breakdowns exist, but the profile already includes them, so the surface is reasonably complete.
get_contact_infoContact Symbols of Wealth StudioAInspectReturns 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 | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden. It transparently lists the types of information returned (email, website, location, how to engage), giving a clear picture of the tool's behavior. It omits minor details like return format, but these are not critical for a simple contact retrieval tool.
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 concise sentences: the first states the action and output, the second provides usage guidance. Every word earns its place, and the key information is front-loaded.
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?
For a simple zero-parameter tool with no output schema and a single sibling, the description covers everything needed: what it does, what it returns, and when to use it. There are no gaps that would hinder an agent's selection or invocation.
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?
The tool has zero parameters and the schema is empty, so schema coverage is trivially 100%. Per rubric, a 0-parameter tool gets a baseline of 4, and no parameter explanation is needed in the description.
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 the tool 'Returns contact information for Symbols of Wealth Studio' with specific content (email, website, location, how to engage). It also distinguishes itself from the sibling tool get_studio_info by noting this is for reaching out rather than browsing the full 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?
Explicit usage guidance is provided: 'Use this when a user wants to actually reach out to or hire Symbols of Wealth Studio, rather than browse the full studio profile.' This clearly indicates when to prefer this tool over the sibling.
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 profileAInspectReturns 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 | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of explaining behavior. It discloses that the tool returns the full studio profile and lists major content sections, setting accurate expectations for the response. Since this is a zero-parameter getter, there are no side effects to disclose, and the description sufficiently conveys that it is an informational retrieval.
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 core purpose is front-loaded in the first few words, but the description includes somewhat verbose marketing language ('senior-creative-director-led AI-powered studio producing world-class brand content at studio scale'). The final sentence is a long list of use cases, but it remains structured and each clause adds relevant 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?
For a tool with no parameters, no output schema, and no annotations, the description is thorough: it specifies the return value's content and offers a wide range of query contexts. It does not mention the sibling tool, but that is not needed for this simple retrieval tool. The description is fully adequate for an agent to invoke it correctly.
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?
The tool has zero parameters, so the baseline is 4. The description implies no inputs are required by saying 'Returns the full studio profile,' and no parameter documentation is needed. It adds nothing beyond the schema, but with zero params that is perfectly acceptable.
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 uses a specific verb and resource: 'Returns the full studio profile for Symbols of Wealth Studio,' immediately clarifying the tool's action and scope. It further differentiates from the sibling tool by enumerating the profile's contents (positioning, services, pricing, work, capabilities), making it clear this is not contact-info retrieval.
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 gives a clear 'Useful for answering questions about...' list that covers relevant domains and industries, providing concrete context for when to use the tool. However, it does not explicitly state when not to use it or contrast it with get_contact_info, so it lacks full exclusion/alternative guidance.
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.
No comments yet. Be the first to start the discussion!
Sign in to create a connector for this server.