Skip to main content
Glama

Get AI activity feed

get_activity

Read the AI agent's recent activity feed in plain language: market scans, position opens/closes (with PnL), and risk-guard events.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of activity items to return (default 10, max 50).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 burden. 'Read' and 'feed' imply a safe, non-mutating operation and the phrase 'in plain language' usefully signals human-readable rather than raw output, but nothing is said about ordering (newest first?), pagination or truncation behavior, or what happens when there is no activity.

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?

One sentence, front-loaded with the verb and resource, with the returned content types listed in a compact trailing clause. Nothing is redundant and nothing needs to be re-read.

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

Completeness3/5

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

For a low-complexity, single-optional-parameter read tool this is close to adequate, and the content enumeration partly compensates for the absent output schema. However, with no annotations and no output schema, an agent still lacks ordering and item-structure information needed to interpret results correctly.

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

Parameters3/5

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

The single parameter's meaning, default of 10, and max of 50 are fully documented in the schema (100% coverage), so the baseline of 3 applies. The description adds no detail about how limit interacts with recency or whether omitted items are silently dropped.

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 names a specific verb and resource ('Read the AI agent's recent activity feed') and enumerates the content it surfaces: market scans, position opens/closes with PnL, and risk-guard events. That enumeration implicitly separates it from point-in-time siblings like get_positions or get_trading_overview, but it never explicitly distinguishes itself from them.

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

Usage Guidelines3/5

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

Usage is only implied by the word 'recent' — an agent can infer this is the chronological feed to consult for recent happenings, but there is no explicit statement of when to prefer it over get_trading_overview or get_positions, and no exclusions or prerequisites.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources