Simpler.Asia

sticky_note_due

Read-onlyIdempotent

Read this tenant's sticky notes whose reminder time (triggers_at) has arrived — the poll the desktop host runs to know what to fire as a local notification, since the web itself has no send channel. Read-only, no arguments: now is always the server's clock, never a caller-supplied value, and only notes with triggers_at set and <= now come back, soonest-due first, capped at 200. NEXT: sticky_note_dismiss clears triggers_at once you've notified, so the same note stops showing up here.

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

Input Schema

Name	Required	Description	Default
`color`	No
`width`	No
`height`	No
`content`	No
`z_index`	No
`position_x`	No
`position_y`	No
`triggers_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavior: now is always the server's clock and never caller-supplied, the filter requires triggers_at to be set, results are soonest-due first, and the result set is capped at 200. These are exactly the traits an agent needs to reason about repeated polling.

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?

Front-loaded with the core verb and scope, and the NEXT pointer is clearly delimited at the end. The middle is a dense em-dash run-on, but every clause (server clock, triggers_at set, sort order, 200 cap) carries distinct information.

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 no-argument read tool with no output schema, the description covers filtering, ordering, and the cap, which is nearly everything needed. It does not sketch the shape of an individual returned note, but that gap is minor given the sibling sticky_note_list/read tools.

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?

Schema coverage is 0% and the schema exposes eight optional properties (color, width, position_x, etc.), which would otherwise be confusing. The description resolves this by declaring 'no arguments' and that now is never caller-supplied, effectively telling the agent to pass nothing — though it would be stronger if it explicitly said the schema properties are ignored for this call.

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?

States a specific verb and resource ('read this tenant's sticky notes whose reminder time has arrived') and frames the exact role: the poll the desktop host runs to fire local notifications. An agent can immediately distinguish it from sticky_note_list, which has no such due-time filter.

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?

Explains the operational context (desktop host polling because the web has no send channel) and explicitly names the follow-up tool, sticky_note_dismiss, plus the condition that triggers it. It does not explicitly warn against using it as a general note listing, but the 'only notes with triggers_at <= now' constraint implies that boundary.

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

All Simpler.Asia tools Inspect

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

Need Help?