Skip to main content
Glama
geter-andru

Andru

by geter-andru
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_founder_wellness

Read-only

Detect early burnout signs from workdays, late nights, and meeting load, then return a risk score and recovery actions. Needs calendar or activity data to score risk.

Instructions

Checks for early signs of burnout from your work days, late nights and meeting load, then gives you a risk score and specific recovery actions. Until Andru has your activity or calendar data, it says the risk is not scored yet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoassessment = burnout risk score + recommendations. dashboard = full wellness data. Default: assessment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.4
    • removedInput schema / properties / userId
      Removed value: -{
-  "description": "The user's Andru account ID. Required for personalized wellness tracking.",
-  "type": "string"
-}
  2. First observedv1.4.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real behavioral context beyond that: it discloses the degraded state where no activity/calendar data exists and the tool reports risk as unscored, which tells the agent how to interpret an empty result. It stops short of explaining how data becomes available or any latency/privacy considerations.

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, front-loaded with the tool's function and followed by the one non-obvious caveat about unscored risk. No filler, no restatement of the title, and every clause carries 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?

With no output schema, the description responsibly characterizes the return values (risk score, specific recovery actions, 'not scored yet' state). It is nearly complete for a zero-required-parameter read tool; the only gap is the unexplained 'dashboard' mode, whose output shape the agent must infer from the 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 coverage is 100% and the single enum parameter 'mode' is fully documented in the schema (assessment vs dashboard). The description never mentions the mode switch or explains what 'dashboard' returns, so it adds no meaning beyond the schema. Baseline 3 applies.

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 names a specific verb and resource ('checks for early signs of burnout') and spells out the signal sources (work days, late nights, meeting load) plus the outputs (risk score and recovery actions). Nothing in the sibling list overlaps with this wellness/burnout function, so an agent can identify it unambiguously.

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?

Usage is implied by the purpose rather than stated: there is no explicit 'use when...' nor any alternative tool to route to. The one piece of guidance present is the data prerequisite ('Until Andru has your activity or calendar data, it says the risk is not scored yet'), which is a useful condition but not a full when-to-use statement.

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

Deploy Server

Other Tools