Skip to main content
Glama

Generate Detailed Burnout Report

generate_burnout_report
Read-only

Generate a comprehensive burnout assessment report with dimension-by-dimension analysis, action plans, and resource recommendations to address workplace stress and improve mental wellness.

Instructions

Generate a comprehensive burnout assessment report with dimension-by-dimension analysis, action plans (immediate/short-term/long-term), and resource recommendations. REQUIRES Starter tier or above (29€/month). Free tier will receive a 403 error. More detailed than analyze_burnout — includes interpretations, status per dimension, and a structured action plan.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
responsesYesArray of 3-20 scored responses across the 3 burnout dimensions.
contextNoContext for personalized report generation
languageNoReport language: 'fr' (French) or 'en' (English)fr
formatNoOutput format: 'json' (structured data) or 'html' (rendered report)json

Implementation Reference

  • The handler logic for 'generate_burnout_report' executes an API call to '/api/v1/generate-report'.
    async ({ responses, context, language, format }) => {
      const result = await apiRequest("/api/v1/generate-report", {
        method: "POST",
        body: JSON.stringify({
          responses,
          context,
          language: language ?? "fr",
          format: format ?? "json",
        }),
      });
    
      if (!result.success) {
        const errMsg = result.error?.message || "Unknown error";
        const hint = result.error?.status === 403
          ? "\n\nHint: This endpoint requires a Starter tier or above (29€/month). " +
            "Upgrade at: https://stresszeroentrepreneur.fr/intelligence-api#pricing"
          : "";
    
        return {
          isError: true,
          content: [
            {
              type: "text" as const,
              text: `Report generation failed: ${errMsg}${hint}`,
            },
          ],
        };
      }
    
      const quotaInfo = result.meta
        ? `\n\nAPI Quota: ${result.meta.quota.used}/${result.meta.quota.limit} (${result.meta.quota.tier} tier)`
        : "";
    
      return {
        content: [
          {
            type: "text" as const,
            text: JSON.stringify(result.data, null, 2) + quotaInfo,
  • Input schema definition for the 'generate_burnout_report' tool.
    inputSchema: {
      responses: z.array(ResponseItemSchema).min(3).max(20).describe(
        "Array of 3-20 scored responses across the 3 burnout dimensions.",
      ),
      context: z.object({
        profession: z.string().max(100).optional().describe("Professional title"),
        hours_per_week: z.number().min(0).max(120).optional().describe("Weekly hours"),
        team_size: z.number().min(0).max(1000).optional().describe("Team size"),
        years_experience: z.number().min(0).max(50).optional().describe("Years experience"),
        company_name: z.string().max(200).optional().describe("Company name (for report header)"),
        employee_name: z.string().max(200).optional().describe("Subject name (for report header)"),
      }).optional().describe("Context for personalized report generation"),
      language: z.enum(["fr", "en"]).default("fr").optional().describe(
        "Report language: 'fr' (French) or 'en' (English)",
      ),
      format: z.enum(["json", "html"]).default("json").optional().describe(
        "Output format: 'json' (structured data) or 'html' (rendered report)",
      ),
    },
  • src/index.ts:219-252 (registration)
    Tool registration for 'generate_burnout_report' using server.registerTool.
    server.registerTool(
      "generate_burnout_report",
      {
        title: "Generate Detailed Burnout Report",
        description:
          "Generate a comprehensive burnout assessment report with dimension-by-dimension analysis, " +
          "action plans (immediate/short-term/long-term), and resource recommendations. " +
          "REQUIRES Starter tier or above (29€/month). Free tier will receive a 403 error. " +
          "More detailed than analyze_burnout — includes interpretations, status per dimension, " +
          "and a structured action plan.",
        inputSchema: {
          responses: z.array(ResponseItemSchema).min(3).max(20).describe(
            "Array of 3-20 scored responses across the 3 burnout dimensions.",
          ),
          context: z.object({
            profession: z.string().max(100).optional().describe("Professional title"),
            hours_per_week: z.number().min(0).max(120).optional().describe("Weekly hours"),
            team_size: z.number().min(0).max(1000).optional().describe("Team size"),
            years_experience: z.number().min(0).max(50).optional().describe("Years experience"),
            company_name: z.string().max(200).optional().describe("Company name (for report header)"),
            employee_name: z.string().max(200).optional().describe("Subject name (for report header)"),
          }).optional().describe("Context for personalized report generation"),
          language: z.enum(["fr", "en"]).default("fr").optional().describe(
            "Report language: 'fr' (French) or 'en' (English)",
          ),
          format: z.enum(["json", "html"]).default("json").optional().describe(
            "Output format: 'json' (structured data) or 'html' (rendered report)",
          ),
        },
        annotations: {
          readOnlyHint: true,
          openWorldHint: true,
        },
      },
Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=true. Description adds critical behavioral context beyond annotations: specific pricing/auth requirement (29€/month Starter tier, 403 error) and output structure details (action plans split by timeframe, resource recommendations). No contradictions with annotations.

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 sentences with zero waste: Sentence 1 states purpose and output contents; Sentence 2 states auth constraint; Sentence 3 distinguishes from sibling. Front-loaded with action verb. No redundant repetition of schema or annotation information.

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

Completeness4/5

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

Given complex nested schema (4 params with nested objects, enums) and no output schema, description adequately explains return value structure (analysis types, action plan categories) and critical auth constraints. Missing only minor details like explicit mention of JSON/HTML format differences handled by schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. Description references 'dimension-by-dimension' which loosely maps to the responses array structure, but does not add specific parameter guidance, syntax help, or examples beyond what the comprehensive schema already provides.

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?

Specific verb 'Generate' + resource 'burnout assessment report' + scope details (dimension-by-dimension analysis, action plans immediate/short-term/long-term, resource recommendations). Explicitly distinguishes from sibling analyze_burnout by stating it is 'More detailed' and lists specific additions (interpretations, status per dimension, structured action plan).

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

Usage Guidelines4/5

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

Provides explicit prerequisite warning (Starter tier required, 403 error for Free tier). Names sibling tool analyze_burnout for comparison ('More detailed than analyze_burnout'). Implicitly guides selection by contrasting depth, though does not explicitly prescribe 'Use this when...' scenarios.

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/gomessoaresemmanuel-cpu/stresszero-mcp'

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