Skip to main content
Glama

Quick Burnout Check

quick_burnout_check
Read-only

Screen for burnout risk by analyzing physical, emotional, and professional effectiveness scores to identify potential wellness concerns.

Instructions

Simplified burnout screening with just 3 scores (one per dimension). Perfect for quick assessments in conversations, chatbots, or triage. Internally calls analyze_burnout with sensible defaults.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
physical_scoreYesPhysical wellbeing score 0-100 (sleep quality, energy, health). Low = burnout risk.
emotional_scoreYesEmotional wellbeing score 0-100 (motivation, stress, mood). Low = burnout risk.
effectiveness_scoreYesProfessional effectiveness score 0-100 (productivity, focus, achievement). Low = burnout risk.
professionNoProfessional role (e.g., 'entrepreneur', 'developer', 'manager')
hours_per_weekNoWeekly working hours (triggers overwork alert if > 50)
languageNoResponse language: 'fr' or 'en'fr

Implementation Reference

  • The handler for the quick_burnout_check tool. It makes an API request to /api/v1/analyze-burnout and formats the response.
    async ({ physical_score, emotional_score, effectiveness_score, profession, hours_per_week, language }) => {
      const result = await apiRequest("/api/v1/analyze-burnout", {
        method: "POST",
        body: JSON.stringify({
          responses: [
            { dimension: "physical", question_id: "overall_physical", value: physical_score, weight: 2 },
            { dimension: "emotional", question_id: "overall_emotional", value: emotional_score, weight: 2 },
            { dimension: "effectiveness", question_id: "overall_effectiveness", value: effectiveness_score, weight: 2 },
          ],
          context: {
            ...(profession && { profession }),
            ...(hours_per_week && { hours_per_week }),
          },
          options: {
            include_recommendations: true,
            include_dimensions: true,
            language: language ?? "fr",
          },
        }),
      });
    
      if (!result.success) {
        return {
          isError: true,
          content: [
            {
              type: "text" as const,
              text: `Quick burnout check failed: ${result.error?.message || "Unknown error"}`,
            },
          ],
        };
      }
    
      const data = result.data as Record<string, unknown>;
      const score = data?.score as Record<string, unknown> | undefined;
      const risk = data?.risk as Record<string, unknown> | undefined;
      const recommendations = data?.recommendations as string[] | undefined;
    
      const summary = [
        `Burnout Score: ${score?.total ?? "N/A"}/100`,
        `Risk Level: ${risk?.level ?? "N/A"} (urgency: ${risk?.urgency ?? "N/A"}/10)`,
        `Dimensions: Physical ${(score?.dimensions as Record<string, number>)?.physical ?? "N/A"} | Emotional ${(score?.dimensions as Record<string, number>)?.emotional ?? "N/A"} | Effectiveness ${(score?.dimensions as Record<string, number>)?.effectiveness ?? "N/A"}`,
        "",
        ...(risk?.factors ? [`Risk Factors: ${(risk.factors as string[]).join(", ")}`] : []),
        "",
        ...(recommendations?.length ? ["Recommendations:", ...recommendations.map((r: string) => `  - ${r}`)] : []),
      ].join("\n");
    
      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: summary + quotaInfo,
          },
        ],
      };
    },
  • src/index.ts:301-333 (registration)
    Registration and input schema definition for quick_burnout_check.
    server.registerTool(
      "quick_burnout_check",
      {
        title: "Quick Burnout Check",
        description:
          "Simplified burnout screening with just 3 scores (one per dimension). " +
          "Perfect for quick assessments in conversations, chatbots, or triage. " +
          "Internally calls analyze_burnout with sensible defaults.",
        inputSchema: {
          physical_score: z.number().min(0).max(100).describe(
            "Physical wellbeing score 0-100 (sleep quality, energy, health). Low = burnout risk.",
          ),
          emotional_score: z.number().min(0).max(100).describe(
            "Emotional wellbeing score 0-100 (motivation, stress, mood). Low = burnout risk.",
          ),
          effectiveness_score: z.number().min(0).max(100).describe(
            "Professional effectiveness score 0-100 (productivity, focus, achievement). Low = burnout risk.",
          ),
          profession: z.string().max(100).optional().describe(
            "Professional role (e.g., 'entrepreneur', 'developer', 'manager')",
          ),
          hours_per_week: z.number().min(0).max(120).optional().describe(
            "Weekly working hours (triggers overwork alert if > 50)",
          ),
          language: z.enum(["fr", "en"]).default("fr").optional().describe(
            "Response language: 'fr' or 'en'",
          ),
        },
        annotations: {
          readOnlyHint: true,
          openWorldHint: true,
        },
      },
Behavior3/5

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

Annotations already declare readOnlyHint=true (safe read operation) and openWorldHint=true (external API call). Description adds value by disclosing the wrapper pattern ('internally calls analyze_burnout with sensible defaults'), helping agents avoid redundant calls. However, lacks details on output format or what constitutes 'sensible defaults'.

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: first defines the tool (simplified screening), second specifies use contexts (chatbots/triage), third explains implementation (wrapper with defaults). Information is front-loaded and every sentence earns its place.

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 100% schema coverage, presence of annotations, and the tool's nature as a simplified wrapper, the description adequately covers intent and delegation pattern. Minor gap: no mention of return value format (though no output schema exists to guide this).

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%, establishing a baseline of 3. Description adds conceptual value by grouping the three required parameters as '3 scores (one per dimension),' providing semantic coherence that individual schema descriptions lack. Also hints at the optional parameters' purpose (profession, hours) through the use-case examples.

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?

Description states specific action ('simplified burnout screening') and resource (burnout/risk assessment). It clearly distinguishes from sibling 'analyze_burnout' by positioning itself as the lightweight alternative ('just 3 scores') and explicitly noting it wraps the other tool.

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 clear contexts for use ('quick assessments in conversations, chatbots, or triage') and explains relationship to sibling ('internally calls analyze_burnout'). Would be 5 if it explicitly stated 'use analyze_burnout instead for detailed analysis' rather than implying it.

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