Skip to main content
Glama

stub

by africa.stub.api
OverviewDiscussionsAdmin

Set todos

set_todos

Create or replace the todo checklist for the current chat. Pass the FULL list of items every time (the stored list is replaced, not merged). Each item has text and a status of "pending", "in_progress", or "done". Use this to plan and track multi-step work — mark an item "in_progress" before starting it and "done" when finished — so progress is visible to the user and survives across sessions. Requires a chatid from an ACTIVE Ask-stub chat session — the id cannot be minted via MCP, so this tool applies only when operating inside a chat.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
todosYesThe FULL checklist (replaces the stored list, not merged).
chatidYesId of the chat whose todo checklist to replace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only provide readOnly and destructive hints, neither indicating any destructive effect. The description transparently explains the replace behavior and the requirement of an active chatid, so no contradiction.

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 description is slightly repetitive in emphasizing 'full list' and 'replaces', but it remains concise and focuses on essential usage and constraints. The main purpose is stated up front.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple tool with only two parameters and no return schema, the description covers all necessary context: what it does, how to use it, and the constraint on chatid. Nothing important is missing.

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

Parameters5/5

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

Both parameters are fully described in the schema, and the description adds important semantics: 'full list' emphasizes the replacement behavior, and the chatid requirement is reinforced with the 'active chat' condition.

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 description clearly states the tool creates or replaces a todo checklist for a chat, specifying the action and resource. It distinguishes itself from sibling tools by focusing on chat-based todo management.

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

Usage Guidelines5/5

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

Explicitly instructs to pass the full list every time, that the list is replaced not merged, and defines allowed statuses. Also notes the chatid must come from an active chat, providing clear when-to-use guidance.

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

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