Skip to main content
Glama
Sign In
nudge

nudge

by davesleal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_stats

Get a summary of total tasks, today's completions, pending items, and overdue tasks for an end-of-day check-in or big-picture view.

Instructions

Get an honest summary of where things stand: total tasks, done today, pending, overdue. Use this for an end-of-day check-in or when the user wants the big picture.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It clearly states that the tool returns a summary of counts (total tasks, done today, pending, overdue), which is transparent for a read-only aggregation tool. No side effects or additional behavior is needed given the simplicity.

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 with no wasted words. The first sentence immediately states the purpose and key outputs, and the second provides use-case guidance. It is front-loaded and efficient.

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?

Given the tool's simplicity (no parameters, no output schema), the description covers the essential information. It provides enough context for the agent to know when to use it versus siblings. However, it could more precisely define terms like 'done today' (e.g., tasks completed today vs. created today).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the schema is fully covered (100%). The description adds value by explaining the nature of the output without needing to detail any inputs. This exceeds the baseline requirement.

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 clearly states the verb 'Get' and the resource 'summary of where things stand', listing specific data points (total tasks, done today, pending, overdue). This distinguishes it from siblings like list_todos (which lists individual tasks) and get_pending_today (which focuses on pending tasks only).

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?

The description explicitly recommends using this tool for 'an end-of-day check-in or when the user wants the big picture,' providing clear usage context. However, it does not mention when not to use it or name alternative tools explicitly, though the purpose differentiation is implied.

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