Skip to main content
Glama

Recent activity

recent_activity
Read-onlyIdempotent

The latest leaderboard moves, follower milestones and new recommendations across the Substack writers Stackblade tracks, newest first, each with a link to the writer's page. kind is all (default), rank (leaderboard moves), rec (new recommendations) or followers (follower milestones). The free feed is delayed.

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

Input Schema

NameRequiredDescriptionDefault
kindNoall (default), rank, rec or followers.

Output Schema

NameRequiredDescriptionDefault
kindYes
eventsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / kind / description
      Added value: +"all (default), rank, rec or followers."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "events": {
      +      "items": {
      +        "properties": {
      +          "at": {
      +            "type": "string"
      +          },
      +          "handle": {
      +            "anyOf": [
      +              {
      +                "type": "string"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ]
      +          },
      +          "kind": {
      +            "type": "string"
      +          },
      +          "recommended": {
      +            "anyOf": [
      +              {
      +                "type": "string"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ]
      +          },
      +          "recommended_url": {
      +            "anyOf": [
      +              {
      +                "type": "string"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ]
      +          },
      +          "text": {
      +            "type": "string"
      +          },
      +          "url": {
      +            "anyOf": [
      +              {
      +                "type": "string"
      +              },
      +              {
      +                "type": "null"
      +              }
      +            ]
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "kind": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "kind",
      +    "events"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world. The description adds behavior the agent cannot see in annotations: results are ordered newest first, every item includes a writer link, and the free feed is delayed — a real staleness caveat that affects how results should be trusted. It stops short of 5 by not saying how many items are returned.

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?

Three sentences, front-loaded with what the feed contains before the parameter explanation and the delay caveat. The main waste is restating the kind values that the schema already enumerates, including the '(default)' marker.

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?

For a single-parameter read tool with an output schema, the description covers content, ordering, item shape (link included), the parameter's meaning, and the data-freshness caveat. Nothing an agent needs in order to call this correctly is missing.

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?

Schema coverage is 100% and the enum values are already listed there, so the baseline is 3. The description does expand the cryptic abbreviations ('rank' = leaderboard moves, 'rec' = new recommendations, 'followers' = follower milestones), which is modest added meaning beyond the schema's terse restatement.

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 resource set (leaderboard moves, follower milestones, new recommendations across the writers Stackblade tracks), states ordering (newest first), and notes each item carries a link to the writer's page. That is far more specific than the title alone. It does not explicitly contrast itself with the sibling 'board' tool, so it stops short of a 5.

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?

Use is implied by the content description and by the kind enumeration, but there is no statement of when to reach for this tool versus 'board' or 'get_follow_links', nor any stated exclusions. An agent can infer it is the activity feed, but must guess the boundary against siblings.

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.