Skip to main content
Glama
Sign In
Dayze MCP

Dayze MCP

by gohluke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Habit Trackers

get_trackers
Read-only

Retrieve active sobriety, streak, and event-backed trackers for the authenticated user, excluding expired countdowns and inactive streaks.

Instructions

Authenticated user live trackers only; expired countdowns and inactive streaks are omitted. Sobriety/streak trackers remain visible at day 0 after a reset. Merges event-backed trackers with the trackers table when present. Requires OAuth or a supported scoped credential. ($0.10; API key required)

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_trackers"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
noteNo
trackersYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.28.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "note": {
+      "type": "string"
+    },
+    "trackers": {
+      "items": {
+        "additionalProperties": true,
+        "description": "A currently active tracker.",
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "trackers"
+  ],
+  "type": "object"
+}
  2. First observedv1.6.2

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already mark readOnly and non-destructive, and the description goes further by revealing specific filtering rules, merge logic with event-backed trackers, day-0 visibility after reset, and credential requirements. It also discloses cost ('$0.10'), which is valuable. No contradiction with annotations; the description enriches transparency substantially.

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?

The description is three sentences, front-loaded with the core scope, then exclusions, an exception, merge behavior, and finally auth/cost. It packs valuable info without excess verbosity, though it is a bit dense with multiple clauses.

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

Completeness5/5

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

With an output schema present and zero params, the description covers all necessary behavioral context: filtering, merging, auth, and cost. Nothing critical is missing for an agent to call this correctly. It is complete for a read-only getter.

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?

There are no parameters, so the description does not need to add parameter meaning. The empty input schema is clear, and the description's auth mention is not parameter-related. The baseline for zero parameters is 4, and the description does not detract from it.

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?

The description clearly states the resource (authenticated user's trackers) and the scope (live only, with exclusions). The verb 'get' is implied but name makes it clear. It distinguishes this from other get_* tools by specifying unique filtering and merging behavior, though no sibling specifically competes.

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?

It conveys when to use this tool by defining what is included and excluded (expired countdowns and inactive streaks are omitted), and states the authentication requirement. It does not explicitly contrast with alternatives, but no direct alternative exists among siblings. The contextual detail about reset behavior adds practical usage nuance.

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