Skip to main content
Glama

Save life-area ratings

save_baseline

Record 1–10 ratings for each life area to establish a baseline for coaching, goal setting, and quarterly reviews. Customize areas by renaming, adding, or removing them.

Instructions

Save 1–10 ratings for each life area. Defaults: health, career, money, relationships, home, hobbies and fun, meaning and growth; people may rename, add or remove areas. Also used at quarterly reviews.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "areas": "<areas>"
    },
    "name": "save_baseline"
  }
}

Input Schema

NameRequiredDescriptionDefault
areasYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the default area set and that areas can be renamed, added or removed, but says nothing about whether a save overwrites a prior baseline, whether partial saves merge, or what happens on re-save.

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?

Three short sentences, front-loaded with the core action and scale. The default-area enumeration is long but earns its place given the free-form object keys; the trailing quarterly-review note is slightly disjointed but still informative.

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?

For a single nested-object mutation with no annotations or output schema, the description covers the key domain semantics (area names, rating scale, default set). It falls short on persistence behavior — overwrite vs merge, required coverage of areas, and any confirmation of what is stored.

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 0%, so the description must compensate, and it does: it explains that the object keys are life-area names (with a default list) and that the 1–10 integers are per-area ratings. It clarifies the semantics of arbitrary propertyNames that the schema leaves bare, though it does not state whether all areas must be supplied.

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?

Names a specific verb and resource ('Save ... ratings for each life area') and pins the value scale at 1–10. This is clearly separable from siblings like save_capacity, save_goal, and save_values, though the description never explicitly contrasts itself with 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?

'Also used at quarterly reviews' gives one usage context, but there is no statement of when to prefer this over save_values or save_capacity, nor any preconditions (e.g., complete an assessment first). Usage is implied rather than prescribed.

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