A
license-
qualityC
maintenanceEnables users to find and contact building tradespeople in France, and lets independent tradespeople create free profiles.
Apache 2.0
fixou
by fr.fixou
Server Details
Create and track quote requests to local French tradespeople (80 trades) on fixou.fr.
- 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.
MCP client
Glama
MCP server
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.
100% free. Your data is private.
Tool Definition Quality
A4.6/5.0
Tool DescriptionsA
Average 4.7/5 across 3 of 3 tools scored.
Server CoherenceA
Disambiguation5/5
Each tool targets a distinct operation: creating a request, retrieving its status, and listing categories. There is no overlap in functionality, making it clear which tool to use for each action.
Naming Consistency5/5
All tools use a consistent verb_noun pattern in snake_case (create_request, get_request, list_categories), making the naming predictable and easy to understand.
Tool Count5/5
With 3 tools, the server is well-scoped for its purpose of managing quote requests. The number is not excessive and each tool serves a necessary function without redundancy.
Completeness3/5
The server covers creation and retrieval of requests, and listing categories, but lacks tools for listing all requests created by an agent, updating a request, or deleting a request. These gaps could hinder streamlined workflows.
Available Tools
3 toolscreate_requestAInspect
Cree une demande de devis Fixou au nom du client final. IMPORTANT : la demande n'est PAS publiee immediatement — elle attend une confirmation par email (double opt-in). L'email est celui du CLIENT FINAL (pas de l'agent) et est obligatoire : le client recevra un email « Confirmez votre demande » avec un lien valable 48 heures ; tant qu'il n'a pas clique, aucun artisan n'est contacte. Apres cet appel, invitez explicitement l'utilisateur a ouvrir sa boite mail et a cliquer sur ce lien de confirmation pour publier sa demande et suivre les reponses sur fixou.fr ; l'agent lui-meme n'a jamais acces a cet espace. La description doit faire au moins 20 caracteres. answers reprend les id de questions et les value d'options du metier (voir list_categories). Renvoie le requestId a utiliser avec get_request.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| Yes | Email du client final (obligatoire) ; il y recevra le lien de confirmation a cliquer pour publier sa demande, puis le suivi. | ||
| phone | No | Telephone du client final (optionnel), transmis aux artisans qu'il choisira. | |
| answers | Yes | Reponses au questionnaire du metier, indexees par `id` de question. Valeur unique (question single) ou tableau de valeurs (question multi), choisies parmi les `value` des options. | |
| postalCode | Yes | Code postal francais du lieu d'intervention (5 chiffres). | |
| description | Yes | Description libre du besoin, en francais, de 20 a 5000 caracteres. | |
| categorySlug | Yes | Slug du metier concerne, obtenu via list_categories. |
Tool Definition Quality
A4.8/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses critical behaviors: request is not published immediately, requires email confirmation (double opt-in), link expires in 48 hours, email is client's not agent's. No annotations to contradict.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Description is relatively long but well-structured: purpose, caveat, email details, post-call instructions, parameter notes. Each sentence adds value; could be slightly more concise but acceptable.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, description mentions returning requestId for use with get_request. Covers min description length, answers format from list_categories, and workflow end-to-end. Very complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% so baseline is 3. Description adds meaning by explaining the workflow for answers and email, e.g., 'answers reprend les id de questions et les value d options'. Adds above baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool creates a quote request for Fixou on behalf of the client. It distinguishes itself from siblings by detailing the double opt-in process and referencing get_request and list_categories.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly advises the agent to invite the user to check email and click the confirmation link after the call. States the agent never accesses the client space, providing clear context for when to use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_requestAInspect
Consulte le statut d'une demande Fixou et les reponses des artisans (nom de l'entreprise, message, prix indicatif, delai, note moyenne). Ne renvoie jamais de coordonnees : celles-ci ne sont communiquees qu'au client final, une fois qu'il a choisi un artisan sur fixou.fr. Une cle API ne peut consulter que les demandes qu'elle a elle-meme creees.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| requestId | Yes | Identifiant de la demande, renvoye par create_request. |
Tool Definition Quality
A4.7/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It discloses behavioral traits: never returns coordinates, explains why, and states API key scoping. Could add more about latency or potential errors, but sufficient.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, no wasted words. First sentence conveys purpose and returned data; second adds constraints. Information is front-loaded.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple 1-param tool with no output schema, the description covers what the tool does, what it returns (listing fields), what it does not return, and access restrictions. No gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers 100% of parameters with a description for requestId. The description adds context that requestId comes from create_request, linking to sibling tool, which adds value beyond schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it checks the status of a Fixou request and artisan responses, listing specific data elements returned. It distinguishes itself from siblings create_request (creation) and list_categories (listing).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states when to use (after creation) and what the tool does not return (contact details), and provides the access constraint that an API key can only query its own requests.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_categoriesAInspect
Liste tous les metiers proposes par Fixou, regroupes par famille, avec le questionnaire propre a chaque metier. A appeler avant create_request : le slug d'un metier devient le categorySlug, et le questionnaire indique les questions a couvrir. Dans create_request, l'objet answers doit utiliser les id de question comme cles et, comme valeurs, les value des options proposees (jamais les libelles).
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Tool Definition Quality
A4.7/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It describes the tool's output structure (metiers, families, questionnaires) and indicates it is a read operation (listing) with no side effects. However, it does not explicitly state read-only nature or mention potential limitations like pagination.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
Three concise sentences, front-loaded with main action, followed by essential usage context. No redundant words; every sentence adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no annotations or output schema, the description provides thorough context: lists all professions with grouping and questionnaire, explains how to use the output in create_request, and specifies data mapping. Complete for a list tool that serves as a prerequisite.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Tool has zero parameters, so baseline is 4. Description correctly omits parameter details as they are unnecessary. The schema coverage is 100% with no properties.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Liste' and the resource 'tous les metiers' with grouping by family and questionnaire. It is specific and distinct from sibling tools (create_request, get_request) which have different purposes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states 'A appeler avant create_request' and explains how the tool's output maps to create_request parameters (slug becomes categorySlug, questionnaire indicates questions). Provides direct guidance on when and how to use this tool.
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!
Related MCP Servers
- AlicenseAqualityDmaintenanceBooks professional home cleaning services anywhere in metropolitan France end-to-end (coverage check, firm quote, booking creation, URSSAF "avance immédiate" enrollment, status polling). End users pay only 50% via SEPA direct debit thanks to the URSSAF immediate tax credit advance — no card payment required.56MIT
- AlicenseBqualityCmaintenanceCompare parcel and letter delivery prices across 60+ carriers in 27 European countries.1MIT
- Alicense-qualityDmaintenanceEnables the calculation and management of hourly-based commercial proposals with persistent storage and interactive statistical visualization. It provides tools to create, list, and analyze quotations for project and maintenance costs directly within Claude.MIT