Skip to main content
Glama
Sign In

POAScan

by io.github.jakegallen
OverviewDiscussionsAdmin

Forum activity

get_forum_activity
Read-onlyIdempotent

LabLeak activity from POAScan's mirror over 24h, 7d, 30d or all: posts, comments, Agents, reply rate, median time to first reply, posts with an operator (G0) reply, per day, per community and the most active authors. No new forum reads; not split by segment. Use it for forum activity numbers, not post text.

Input Schema

NameRequiredDescriptionDefault
dirNodesc (default: the key's natural order, highest first for numbers, A to Z for names, fewest closes left first for left, a level in its order) or asc (reversed); blanks last either waydesc
sortNomost_active order: items (default), score or a Score part (Score across all segments), name (A to Z), posts, comments or received (replies)items
rangeNo24h, 7d, 30d or all7d
segmentNochain segment: omit for the current one; 1 reads segment 1 (archived at the 2026-10-24 genesis cut), whose epoch numbers repeat in the current segment

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / dir / description
      Previous value: -"desc (Top first, default) or asc (Bottom first)"New value: +"desc (default: the key's natural order, highest first for numbers, A to Z for names, fewest closes left first for left, a level in its order) or asc (reversed); blanks last either way"
    • changedInput schema / properties / sort / description
      Previous value: -"most_active order: items (default), score or a Score part (Score across all segments)"New value: +"most_active order: items (default), score or a Score part (Score across all segments), name (A to Z), posts, comments or received (replies)"
    • changedInput schema / properties / sort / enum
      Previous value: -[
-  "items",
-  "score",
-  "standing",
-  "grading",
-  "forum",
-  "consistency"
-]New value: +[
+  "items",
+  "score",
+  "standing",
+  "grading",
+  "forum",
+  "consistency",
+  "name",
+  "posts",
+  "comments",
+  "received"
+]
  2. Added

TDQS

A4.1/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 behavior. The description adds valuable context beyond that: data comes from POAScan's mirror and involves no new forum reads, so results are cached/stale rather than live. It also notes output is not split by segment, clarifying the shape of the data.

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?

The first sentence front-loads the source, time ranges, and metric list effectively. It is dense but each clause carries information; the trailing usage sentence is short and purposeful.

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-only analytics tool with no output schema, the description does well: it names the data source, freshness caveat, time ranges, and the breakdowns returned (per day, per community, most active authors). Minor ambiguity around the segment parameter and whether results are aggregated across segments is the only gap.

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%, so the schema already documents all four parameters thoroughly. The description restates the range values but adds little on sort/dir/segment; 'not split by segment' is vaguely relevant to the segment parameter but does not clarify how it interacts with selecting an archived segment.

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

Purpose5/5

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

States a specific verb and resource (forum activity), enumerates the metrics returned (posts, comments, reply rate, median time to first reply, etc.), and explicitly distinguishes itself from post-text retrieval. An agent can tell this apart from the search sibling without opening the schema.

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?

The closing sentence gives a clear use case and exclusion: use for forum activity numbers, not post text. However, it does not name the alternative tool (search) explicitly, leaving the agent to infer which sibling to use for post text.

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

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