Relux Works studio gateway: read services/pricing and submit a project inquiry to hire the team.
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.4/5 across 2 of 2 tools scored. Lowest: 3.8/5.
The two tools have completely distinct purposes: one retrieves pricing/service information, the other submits a quote request. There is no overlap or ambiguity between them.
Both tool names follow the same verb_noun pattern with underscores (get_services_pricing, request_project_quote), maintaining consistent and predictable naming.
With only 2 tools, the server feels thin, but the narrow scope (pricing info and quote requests for Relux Works) makes the count borderline acceptable rather than excessive.
The tools cover the core workflow of retrieving pricing and requesting a quote, but lack features like quote status tracking or management, which is a minor gap agents can work around.
get_services_pricingGet services and pricingAReturns Relux Works services, fixed-price packages, company facts, selected work, supported languages, and market-specific planning prices. Tool and service identifiers remain in English.
| Name | Required | Description | Default |
|---|---|---|---|
| market | No | Preferred market or ISO country code, for example us, gb, de, ae, sa, sg, il, ca, or au. | |
| preferred_language | No | Preferred BCP 47 language for regional filtering and the agent presentation, for example de, fr, ar, ar-AE, fa, or he. Canonical catalog prose remains in English. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover read-only, idempotent, and non-destructive behavior. The description goes beyond this by disclosing that tool and service identifiers remain in English, adding useful behavioral context about language handling. It also notes market-specific pricing, which is not evident from annotations alone.
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 two sentences long, front-loaded with the primary action, and contains no filler. Each sentence earns its place: the first enumerates what is returned, the second clarifies a language nuance.
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?
There is no output schema, so the description must explain return values. It lists the major categories of returned data, which gives a good overall picture. However, it doesn't specify the structure (e.g., whether items are grouped) or clarify ambiguous terms like 'selected work,' leaving some gaps for a tool without an output schema.
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?
Schema description coverage is 100%, so both 'market' and 'preferred_language' are already well-documented with examples and purpose. The description adds minimal extra meaning about parameters, only hinting that prices are market-specific, which is sufficient given the strong schema.
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 the specific verb 'Returns' and names the resource: Relux Works services, fixed-price packages, company facts, selected work, supported languages, and market-specific planning prices. It clearly distinguishes from the sibling tool 'request_project_quote' by focusing on information retrieval rather than quote submission, though it does not explicitly contrast them.
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 implies this tool is for fetching service and pricing information, and the sibling name 'request_project_quote' hints at an alternative for quote requests. However, there is no explicit when-to-use or when-not-to-use guidance, nor are alternatives mentioned in the text itself.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
request_project_quoteRequest a project quoteACreates and immediately sends an external project inquiry to a private Relux Works Telegram chat for human review. Do not call it to test the connector or demonstrate MCP. Build the summary from known conversation context, ask only for missing details, obtain a real user-provided or user-confirmed reply route to the decision maker or an accountable relay agent, and show the complete draft including that route. Before calling, provide https://relux.works/en/privacy-policy/ and obtain explicit user consent. Never invent or infer contact details. The current MCP chat is not a reply route. A human replies within one business day with a recommended package and a fixed-price quote.
| Name | Required | Description | Default |
|---|---|---|---|
| market | No | Client market or country code | |
| summary | Yes | What the user wants to build or fix, current state, goals (required) | |
| timeline | No | Desired timeline or deadline | |
| budget_usd | No | Approximate budget in USD, if known | |
| client_name | No | Name of the person or company | |
| project_type | No | Closest project category | |
| contact_email | No | Real, reachable decision-maker email provided or explicitly confirmed by the user. Never invent or infer it. Legacy shorthand for reply_contact with channel=email and recipient=decision_maker. Reserved example and test domains are rejected. | |
| reply_contact | No | External route provided or explicitly confirmed by the user that a Relux Works human can use to reach the decision maker or a relay agent. Never invent or infer it. The current MCP session, chat, or inquiry ID does not qualify. | |
| consent_confirmed | Yes | Set to true only after the user has reviewed the complete inquiry and reply route, received the privacy notice URL, and explicitly approved submission to Relux Works. | |
| preferred_language | No | Language preferred for the human reply |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses significant behavioral traits beyond the destructiveHint annotation: it sends data externally, requires explicit user consent and privacy policy review, forbids inventing contact details, notes the current MCP chat is not a reply route, and states a human replies within one business day. This is far richer than the annotations alone.
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 a single dense paragraph where every sentence delivers essential information—purpose, misuse warning, process steps, privacy/consent, and expectations. No fluff or redundancy; it is appropriately sized for a high-stakes external action.
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 complex tool with 10 parameters, nested reply_contact object, and no output schema, the description covers purpose, misuse, step-by-step submission requirements, consent, privacy policy, and the expected human follow-up. It is comprehensive enough for an agent to invoke correctly without additional external knowledge.
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?
Schema description coverage is 100%, so baseline is 3. The description adds crucial guidance for key parameters: summary must be built from known conversation context, consent_confirmed requires explicit approval after privacy notice, and contact fields must be user-provided or confirmed, never invented. It doesn't elaborate on optional fields, but they are covered by the schema.
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 states a specific action: 'Creates and immediately sends an external project inquiry to a private Relux Works Telegram chat for human review.' This clearly distinguishes it from the sibling tool get_services_pricing, which is about retrieving pricing information.
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?
It explicitly warns against misuse: 'Do not call it to test the connector or demonstrate MCP.' It also provides clear preconditions: build summary from conversation context, ask only for missing details, obtain a user-confirmed reply route, show the draft, and get explicit consent after sharing the privacy policy.
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!