Skip to main content
Glama
Sign In

CheckFlow

by io.checkflow
OverviewDiscussionsAdmin

Get task snooze

get_task_snooze
Read-onlyIdempotent

Whether this task is snoozed for the member the connection is acting for, and until when. A snooze is personal: it hides the task from that member's own tasks grid and changes nothing anybody else sees, which is why it is not on the task read.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "checklistKey": "<checklistKey>",
      "taskKey": "<taskKey>"
    },
    "name": "get_task_snooze"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskKeyYesThe task's key, a GUID.
checklistKeyYesThe checklist's key, a GUID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnly and idempotent. The description adds genuinely new behavior: the snooze is scoped to the acting member, hides the task from that member's grid only, has no effect for others, and is therefore absent from the task read. It does not disclose the return shape (e.g. what a non-snoozed task yields), which is a minor gap given no output schema exists.

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?

Two sentences, front-loaded with what is returned, followed by the scoping rationale. The final clause explaining the omission from the task read earns its place, though the second sentence is dense enough that a tighter phrasing is possible.

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 correctly states what comes back (whether snoozed and until when) and why it is separate from the task read. It is nearly complete for a two-parameter read, but leaves the null/not-snoozed case and the standalone-task counterpart unspecified.

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

Parameters3/5

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

Schema coverage is 100% and both GUID parameters are documented in the schema, so the description need not repeat them. It adds no syntax or format detail beyond the schema, making the baseline 3 appropriate.

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 first sentence states precisely what the tool returns: the acting member's snooze state for a task and its end time. The second sentence distinguishes it from the task read (get_task) by explaining that snooze is personal. The verb 'get' is only implied by the phrasing 'Whether... and until when', which is slightly indirect.

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

Usage Guidelines3/5

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

It implies when the tool is needed (personal snooze state, which the task read omits), but never explicitly says 'call this when...' or names the sibling get_standalone_task_snooze for standalone tasks. There is also no guidance on when not to call it versus set_task_snooze or end_task_snooze.

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

All CheckFlow toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources