AlphaWeb

activity_list

Read-only

Workspace audit/notification feeds.

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": {
      "workspace": "<workspace>"
    },
    "name": "activity_list"
  }
}

Input Schema

Name	Required	Description	Default
`feed`	No
`view`	No
`actor`	No
`limit`	No
`since`	No
`until`	No
`cursor`	No
`domain`	No
`module`	No
`sources`	No
`agent_run`	No
`workspace`	Yes
`severities`	No
`event_types`	No
`resource_id`	No
`unread_only`	No
`actor_user_id`	No
`resource_type`	No
`actor_teammate_id`	No
`initiated_by_user_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 23, 2026
- addedInput schema / properties / actor_teammate_id
```
Added value: +{
+  "format": "uuid",
+  "type": "string"
+}
```
- addedInput schema / properties / actor_user_id
```
Added value: +{
+  "format": "uuid",
+  "type": "string"
+}
```
- addedInput schema / properties / initiated_by_user_id
```
Added value: +{
+  "format": "uuid",
+  "type": "string"
+}
```
First observedOct 23, 2026

TDQS

D1.8/5.0

Behavior2/5

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

Annotations establish that this is a read-only, non-destructive, closed-world operation, but the description adds no behavioral context beyond the phrase "audit/notification feeds." It does not explain pagination, feed semantics, view modes, or what the read operation returns, which matters for a 20-parameter activity query.

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

Conciseness2/5

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

The description is extremely short, but the brevity is under-specification rather than concise usefulness. It is a single fragment that does not front-load an action, scope, or routing guidance.

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

Completeness1/5

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

With 20 parameters, no output schema, and zero schema description coverage, the description is completely inadequate for the tool's complexity. It does not explain required workspace scoping, feed selection, filtering, pagination, or return behavior.

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

Parameters1/5

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

The schema has 20 parameters with 0% description coverage, so the description carries the full burden of explaining parameters, but it says nothing about feed, view, actor, since, until, cursor, sources, severities, event_types, or any other field. This is a severe gap for an agent trying to invoke the tool correctly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a four-word noun phrase, "Workspace audit/notification feeds," with no verb indicating whether the tool lists, reads, summarizes, or exports activity. It gestures at the resource domain but does not clearly distinguish this from siblings such as notifications_update or other workspace-scoped list tools.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool instead of alternatives, no explanation of when to choose the notifications feed versus the audit_log feed, and no mention of prerequisites. The agent is left to infer usage entirely from the tool name and schema.

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

All AlphaWeb tools Inspect

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

Need Help?