Skip to main content
Glama
Sign In
mcp-screen

mcp-screen

by ashark-ai-05
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

reply_oldest_pending

Answers the oldest pending canvas note in one click, optionally limited to a project canvas, so unanswered notes are resolved in order.

Instructions

One-click: answer the oldest unanswered note on the canvas (see read_canvas → pendingQuestions). Use when the human said "answer my notes" or a hook told you notes are waiting and you can answer the first one now. Optional canvas limits to that project.

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": {
      "text": "<text>"
    },
    "name": "reply_oldest_pending"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesYour answer (plain text, short).
canvasNoOptional project canvas id; default is the oldest across all canvases.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. 'One-click' hints that the reply is sent immediately with no confirmation step, which is useful, but it does not say whether the note is then marked answered, whether the action is reversible, or what happens if no pending note 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 compact sentences with the action stated first and the usage condition second. 'One-click' is slightly promotional filler, but nothing else is wasted.

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 simple two-parameter write tool with no output schema, the description supplies the trigger, the selection rule, and the recommended prerequisite (read_canvas). The main remaining gap is post-condition behavior — whether the note is consumed or marked answered — which an agent might want before calling.

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 description coverage is 100%, so the schema already explains both 'text' and 'canvas'. The description only echoes the canvas scoping ('limits to that project', default oldest across all canvases), adding little beyond the structured fields; baseline 3 is 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 description uses a specific verb+resource ('answer the oldest unanswered note on the canvas') and defines the selection rule (oldest, across all canvases unless scoped). That distinguishes it from generic reply tools, though it never explicitly names the sibling reply_annotation, so an agent must infer the difference.

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?

It gives concrete triggering conditions: the human said 'answer my notes', or a hook signalled notes are waiting and the first can be answered now. It also points to read_canvas → pendingQuestions as the pre-read. No explicit when-not or exclusion against reply_annotation, which keeps it from a 5.

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