Skip to main content
Glama
Sign In
workflow-hints

workflow-hints

by PradellaNicolas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

hints_get_daily_summary

Get today's workflow summary with structured counters and timing, covering sessions, edits, MCP usage, and plans to review progress and identify next actions.

Instructions

Get structured counters and timing for today.

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": "hints_get_daily_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.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 burden of explaining behavior. 'Get' implies a read-only retrieval and 'for today' defines the time scope, which is helpful. However, it does not disclose whether the summary resets daily, what timezone is used, or whether any internal state is affected.

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?

The description is a single, focused sentence with no filler. It front-loads the verb and object, then adds the key qualifiers 'structured counters' and 'timing'.

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?

For a parameterless, read-only summary tool, the description is nearly complete: it names the data returned and the temporal scope. It could be slightly richer by clarifying what 'timing' refers to or the exact daily boundary, but nothing critical is missing for basic invocation.

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 has zero parameters, so the schema fully covers parameter semantics. The description does not need to add parameter detail, and the baseline for zero-parameter tools applies.

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 verb 'get' and the resource 'daily summary', and specifies the content as 'structured counters and timing'. It does not explicitly differentiate from sibling tools, but the resource and scope are specific enough to avoid serious ambiguity.

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

Usage Guidelines2/5

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

No guidance is given about when to use this tool versus siblings like hints_get_context or hints_record_event. There are no exclusions, prerequisites, or alternative suggestions beyond what the name itself implies.

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