Skip to main content
Glama

activity

Check current builds, installs, and programmer use, including who started each task, before beginning work that needs the same add-on or programmer.

Instructions

What is in progress right now (builds, installs, programmer use) and who started it.

The user can also start actions from the dashboard, so check this before starting work that needs the same add-on or the programmer.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It implies a non-mutating inspection and hints at the return contents (in-progress operations and their initiator), but it does not explicitly state that nothing is modified, nor describe shape, latency, or behavior when nothing is running.

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?

Two short sentences, the scope stated first and the operational reason second. Nothing is redundant and no padding is present.

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 zero parameters, no annotations and no output schema, the description still conveys what is returned and why it matters for concurrency avoidance. The main residual gap is that returned fields and the empty-state behavior are not described, which matters slightly more because no output schema exists.

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?

The tool takes zero parameters, so there is no parameter semantics to document and the baseline applies. The description correctly implies no arguments are needed.

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?

States a specific resource and scope: current in-progress work (builds, installs, programmer use) plus who started it. An agent can tell this is a snapshot of live activity rather than a status of a specific job, though it never names the sibling tools (build_status, install_status) it overlaps with, so differentiation is left implicit.

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?

Gives a concrete when-to-use rule: call it before starting work that needs the same add-on or the programmer, because actions may already be running from the dashboard. No when-not guidance or explicit named alternative is given, which keeps it short of a 5.

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