Skip to main content
Glama
Sign In

ActivitySmith

by com.activitysmith
OverviewDiscussionsAdmin

List Live Activities

list_live_activities
Read-only

List Live Activities sent from this account, newest first, with their status, Tags, and latest content. Use it to review recent activity or find an activity_id; for one known activity, use get_live_activity. To change a running activity, use the stream tools such as set_live_activity_stream. Equal creation times use descending ID order. Defaults: limit 50, offset 0; maximum limit 100. Continue with meta.next_offset and the same filters; stop when it is null. Results can change between requests.

Input Schema

NameRequiredDescriptionDefault
tagsNoOnly return activities with these Tags, up to 20 slugs such as deploys (see list_tags). Matching is case-insensitive.
limitNoMaximum activities to return, 1-100. Defaults to 50.
offsetNoNumber of activities to skip. Use meta.next_offset from the previous page. Defaults to 0.
statusNoOnly return activities with this status: in_progress, completed, cancelled, or expired. Omit for all.
tag_modeNoHow tags combine: all (default) requires every listed Tag, any requires at least one.all

Output Schema

NameRequiredDescriptionDefault
dataYes
metaYes

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?

Beyond the read-only annotations, it discloses ordering and tie-breaking, pagination continuation via meta.next_offset, stopping condition, and that results can change between requests. This is unusually rich behavioral context for a list endpoint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with purpose and routing guidance, then gives ordering and pagination mechanics. Every sentence contributes either selection guidance or invocation semantics, with no filler.

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 read-only annotations, full schema coverage, and an output schema, the description supplies all the additional context an agent needs: sibling routing, ordering, defaults, pagination flow, and data freshness. Nothing material is missing.

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 100%, so the schema already documents all five parameters well. The description adds useful pagination semantics and repeats key defaults and the maximum limit, but it does not add much detail for tags, status, or tag_mode beyond what the schema provides.

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 gives a specific verb and resource ('List Live Activities') and states account scope, ordering, and returned fields. It also explicitly distinguishes this tool from get_live_activity and the stream tools, so an agent can select it without inspecting siblings.

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?

It provides explicit when-to-use guidance: review recent activity or find an activity_id. It also names the alternative for a single known activity and the stream tools for changing a running activity, covering the relevant sibling routes.

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

All ActivitySmith toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources