Skip to main content
Glama

Get streak

get_streak
Read-onlyIdempotent

Read the user's Habidu streak as the app shows it: the current run of consecutive days with at least one completed task, plus the longest streak, stars and banked streak freezes, and the last completed date. Use it to celebrate progress or answer "how is my streak"; it does not list tasks (get_tasks). A new user returns streak 0. Read-only, takes no parameters.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered; the description still adds value by disclosing the return payload fields and the edge case that a new user returns streak 0. It does not discuss ownership/auth scope or whether the streak is computed in a particular timezone, which would round it out.

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 short sentences, front-loaded with the resource and return contents, then usage, then the sibling exclusion. No filler or redundant restatement of the title.

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?

For a zero-parameter read tool with no output schema, the description carries the needed burden by listing the returned fields and the new-user zero case. An agent has everything required to call it and interpret the result.

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?

Zero parameters, so the baseline is 4. The description confirms "takes no parameters," which is consistent with the empty schema and prevents an agent from hunting for optional filters.

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?

Names a specific resource (the user's Habidu streak) and enumerates exactly what it returns: current consecutive-day run, longest streak, stars, banked freezes, and last completed date. It explicitly distinguishes itself from get_tasks, so an agent can route correctly without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete when-to-use ("celebrate progress or answer 'how is my streak'") and an explicit when-not-to-use with the named alternative ("it does not list tasks (get_tasks)"). Nothing about selection is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources