Skip to main content
Glama
Noosbai
by Noosbai

Exporter le feedback pour la communauté

export_feedback

Export anonymized 3D printing feedback to contribute to community knowledge. Removes file paths and generalizes printer names for secure sharing via GitHub PR or other channels.

Instructions

Exporte tes retours d'impression de manière anonymisée pour contribuer à la base de connaissances communautaire. Supprime les chemins de fichiers et généralise le nom d'imprimante. Le JSON résultant peut être partagé via GitHub PR ou autre canal.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Main handler for export_feedback tool. Registers the tool with MCP server, loads user feedback, anonymizes it using exportForCommunity(), and returns a JSON export ready for community contribution via GitHub PR.
    export function registerExportFeedback(server: McpServer) {
      server.registerTool(
        "export_feedback",
        {
          title: "Exporter le feedback pour la communauté",
          description:
            "Exporte tes retours d'impression de manière anonymisée pour contribuer " +
            "à la base de connaissances communautaire. Supprime les chemins de fichiers " +
            "et généralise le nom d'imprimante. Le JSON résultant peut être partagé " +
            "via GitHub PR ou autre canal.",
          inputSchema: {},
        },
        async () => {
          try {
            const feedbacks = await loadFeedback();
    
            if (feedbacks.length === 0) {
              return {
                content: [{
                  type: "text" as const,
                  text: "Aucun feedback à exporter. Imprime d'abord et note tes résultats !",
                }],
              };
            }
    
            const anonymized = exportForCommunity(feedbacks);
            const exportData = {
              exportDate: new Date().toISOString().split("T")[0],
              printCount: anonymized.length,
              data: anonymized,
            };
    
            const json = JSON.stringify(exportData, null, 2);
    
            const lines = [
              "## Export communautaire prêt",
              `**Prints exportés** : ${anonymized.length}`,
              "",
              "Données anonymisées (pas de chemins, pas de noms exacts) :",
              "",
              "```json",
              json,
              "```",
              "",
              "Pour contribuer :",
              "1. Copie le JSON ci-dessus",
              "2. Ouvre une PR sur le repo PrusaMCP",
              "3. Ajoute tes données dans `community-contributions/`",
              "",
              "_Merci de contribuer à l'amélioration des recommandations pour tout le monde !_",
            ];
    
            return {
              content: [{ type: "text" as const, text: lines.join("\n") }],
            };
          } catch (error) {
            return {
              isError: true,
              content: [{
                type: "text" as const,
                text: `Erreur : ${error instanceof Error ? error.message : String(error)}`,
              }],
            };
          }
        },
      );
    }
  • src/index.ts:21-21 (registration)
    Import statement for registerExportFeedback function from feedback.ts module.
    import { registerSubmitFeedback, registerFeedbackStats, registerExportFeedback } from "./tools/feedback.js";
  • src/index.ts:55-55 (registration)
    Registration call that activates the export_feedback tool on the MCP server instance.
    registerExportFeedback(server);
  • Helper function exportForCommunity that maps and anonymizes an array of PrintFeedback objects to AnonymizedFeedback format for community sharing.
    export function exportForCommunity(
      feedbacks: PrintFeedback[],
    ): AnonymizedFeedback[] {
      return feedbacks.map(anonymizeFeedback);
    }
  • Helper function anonymizeFeedback that strips sensitive information (file paths, exact printer names, timestamps) and generalizes printer type using generalizePrinter() function.
    export function anonymizeFeedback(feedback: PrintFeedback): AnonymizedFeedback {
      return {
        material: feedback.material.toUpperCase(),
        printerType: generalizePrinter(feedback.printer),
        nozzle: feedback.nozzle,
        goal: feedback.goal,
        layerHeight: feedback.layerHeight,
        infillPercent: feedback.infillPercent,
        printSpeed: feedback.printSpeed,
        nozzleTemp: feedback.nozzleTemp,
        bedTemp: feedback.bedTemp,
        supportUsed: feedback.supportUsed,
        qualityScore: feedback.qualityScore,
        adhesionScore: feedback.adhesionScore,
        strengthScore: feedback.strengthScore,
        overallScore: feedback.overallScore,
        issues: feedback.issues,
      };
    }
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden and discloses key behavioral traits: anonymization process (removes file paths, generalizes printer names), output format (JSON), and sharing capabilities (GitHub PR or other channels). It doesn't cover error handling or performance aspects, but provides substantial operational context.

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?

Two sentences efficiently convey purpose, transformation process, and output usage. The description is appropriately sized and front-loaded with the core function, though minor redundancy exists between 'anonymisée' and the specific anonymization steps mentioned.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and 0 parameters, the description provides good behavioral context but lacks details about what specific feedback data is exported, potential limitations, or error conditions. It's adequate for a simple export tool but could be more comprehensive about the scope and constraints.

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?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately focuses on behavioral aspects rather than parameter details, meeting the baseline expectation for zero-parameter tools.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('exporte') and resource ('tes retours d'impression'), specifying anonymization and contribution to community knowledge base. It distinguishes from sibling 'submit_feedback' by focusing on export rather than submission, though not explicitly contrasting them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context ('pour contribuer à la base de connaissances communautaire') and suggests sharing methods ('via GitHub PR ou autre canal'), but doesn't explicitly state when to use this versus alternatives like 'submit_feedback' or other data export tools. Guidance is present but not comprehensive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Noosbai/PrusaMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server