Skip to main content
Glama
Sign In

Weft

by com.letsweft
OverviewDiscussionsAdmin

Report Progress

report_progress
Idempotent

Say you are still working. Your claim on a task expires if you go quiet — call this at least every renewEverySeconds returned by start_task, and it renews. Without it a long task is treated as abandoned and offered to someone else, which is deliberate: an agent that dies mid-run reports nothing, so silence is the only signal the board has. Also the place to say you are blocked or waiting on the user.

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": {
      "runId": "<runId>",
      "leaseToken": "<leaseToken>"
    },
    "name": "report_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoOne line on where you are
runIdYesThe runId returned by start_task
statusNo'working' (default) renews the claim; the others park the task for the human
learningsNoUp to 3 lessons worth remembering BEYOND this task — "estimates on frontend tasks run 2x low", "this user rejects copy with exclamation marks". 1–3 sentences each; optionally {trigger, content} where trigger says when to recall it. They surface in every future get_my_work, to every client on this board, and in the planner's own prompt — and nothing here takes one back. Write only what will still be true next month, and nothing about a person you would not put in writing. Not a work log — report progress in `note`/`outcome` instead.
leaseTokenYesThe leaseToken returned by start_task

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  2. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Well beyond the annotations, it discloses the consequence of silence (the claim expires and the task is treated as abandoned and offered to someone else) and explains why that is deliberate. This is exactly the kind of operational risk context an agent needs to keep a lease alive.

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?

The imperative action is front-loaded and the rationale follows in a compact three-sentence block. The middle sentence is long and clause-heavy, but every clause carries a distinct fact (cadence, consequence, design intent), so little 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?

With five parameters, no output schema, and annotations already covering the safety profile, the description supplies the lease lifecycle and cadence an agent must know. It stops short of describing what the call returns or how to detect an expiring lease before it lapses.

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 runId, leaseToken, note, status, and learnings are already documented; the baseline is 3. The description adds only incidental param semantics (the renewEverySeconds timing signal and that blocked/needs_input park the task), largely duplicating what the schema's status description already says.

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 opening line 'Say you are still working' states the action in plain terms, and the second sentence pins it to the lease-renewal mechanism ('call this ... and it renews'). It is clearly distinguishable from siblings like start_task, complete_task, and request_input.

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 an explicit cadence rule (at least every renewEverySeconds returned by start_task) and an explicit alternative use ('the place to say you are blocked or waiting on the user'). It does not name when to prefer request_input over the needs_input status, so the routing between those two overlapping mechanisms is left slightly ambiguous.

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

All Weft 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