Skip to main content
Glama

Where am I?

get_status

Call this first in every session to retrieve your current phase, next reflection question, and everything due today—weekly reviews, habit-strength checks, decisions, and lapsed habits.

Instructions

Call first in every session. Returns the current phase, the next reflection question, and anything due today: weekly review, monthly habit-strength checks, quarterly review, upcoming decisions and lapsed habits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden; "Returns" makes clear it is a read-only aggregation with no mutation implied. It enumerates what comes back, which is the main behavioral concern for a zero-parameter call. It does not discuss auth, timezone scoping of "due today," or response shape, but for a no-arg read tool that is a minor gap.

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, zero waste, with the actionable directive front-loaded before the return-value enumeration. Every clause adds information an agent would otherwise have to guess.

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 does the work of listing returned fields, which is the right compensation for a zero-param aggregate tool. It leaves open the exact response structure and how "due today" is bounded, but an agent has enough to call it correctly.

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 tool takes zero parameters, so there is no parameter meaning to add and the baseline is 4. The description correctly implies no input is needed by framing the call as a bare session-opening step.

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?

States a concrete verb and an enumerated payload: current phase, next reflection question, and due-today items (weekly review, monthly checks, quarterly review, decisions, lapsed habits). This distinguishes it from siblings like get_plan, get_method, and open_dashboard without needing their schemas.

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?

"Call first in every session" gives an explicit, unambiguous trigger for when to use it. It stops short of naming an alternative or a when-not condition, but the ordering directive is strong enough that an agent knows exactly where this belongs in a workflow.

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