Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

agents_activity

Read-onlyIdempotent

See what you — or another agent in your workspace — actually did over a time window: messages sent, documents created, calls made, plus a summary (run counts, per-day, top tools). Use this to answer 'what did I do today / yesterday / last week / in the last hour?' or 'what did do?' with real data instead of guessing.

Omit agent for your own activity, or pass another workspace agent's name, slug, or id. Pass since/until as ISO datetimes (e.g. '2026-06-03T09:00:00') for sub-day windows like the last hour, or plain dates ('2026-06-03') for whole days — compute them from the current date/time you were given. Defaults to the last 24h. Traces are retained 30 days.

Times are interpreted as UTC — if the current time you were given is in another timezone, convert to UTC before passing since/until.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agentNoTarget agent: name, slug, or numeric id. OMIT for yourself.
limitNoMax actions / recent runs to return.
sinceNoWindow start — ISO datetime or date. OMIT for last 24h.
untilNoWindow end — ISO datetime or date (exclusive day-end for a bare date). OMIT for now.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
+  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
+  "type": "integer"
+}
  2. Added
  3. Removed
  4. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive behavior, so the description focuses on useful extras: 30-day trace retention, a default 24h window, and the UTC interpretation of since/until — all genuinely beyond the structured fields. It omits explicit auth/error behavior, but retention and timezone semantics are real added context.

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?

Front-loaded with what it does, then parameters, then the timezone caveat — a sensible order. It is slightly padded (the 'compute them from the current date/time you were given' instruction recurs near the timezone note), but every sentence carries useful information.

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 read tool with no output schema, it covers defaults, retention, timezone handling, and a sketch of the return shape (run counts, per-day, top tools), which is enough to call it correctly. The only uncovered item is in_workspace, and its session-scoping caveat is left to the schema.

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 baseline is 3, but the description adds real meaning beyond the schema: ISO vs bare-date formats for since/until, how to compute them from the supplied current time, and that omitting `agent` means 'yourself'. It does not touch in_workspace or limit, so not a full 5.

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 gives a specific verb and resource — 'see what you or another agent actually did over a time window' — and enumerates the returned content (messages, documents, calls, plus a run-count/per-day/top-tools summary). It is unambiguous what the tool produces, but it never names or contrasts a sibling (e.g. agents_traces_list / agents_traces_stats), so an agent must infer the boundary from the returned payload.

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?

Usage is explicit and framed around concrete questions ('what did I do today / yesterday / last week / in the last hour?' or 'what did <agent> do?'), which tells the agent exactly when to reach for it. There is no exclusion guidance or routing to overlapping trace tools, so it stops 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.

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