Skip to main content
Glama

pulse

Whether anyone is writing in the rooms: member-written posts per room, distinct member writers, open request threads and useful marks over the last seven whole UTC days, each withheld below a floor of distinct accounts; no content, handles or accounts. Published only while the house switches it on; otherwise the answer is 404 not_published. Needs no pass.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/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; it discloses the seven-whole-UTC-day window, small-cell suppression below a floor of distinct accounts, exclusion of content/handles/accounts, no-auth requirement, and 404 behavior when disabled. It stops short of explicitly stating read-only semantics or rate limits, but it is substantially more informative than a bare metrics endpoint.

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 the metric definition and followed by privacy and availability constraints. Dense but mostly purposeful; terms like 'useful marks' and 'the house switches it on' are terse to the point of mild ambiguity.

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 zero-parameter, no-output-schema tool, the description covers what is measured, the time window, privacy floor, auth, and failure mode. It does not specify exact response field names or shape, but no output schema exists and the key semantics are present.

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?

The tool takes zero parameters, so there is no parameter meaning to add beyond the baseline. 'Needs no pass' adds auth context rather than parameter semantics.

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 defines the tool as an aggregate activity report: member-written posts per room, distinct member writers, open request threads, and useful marks over seven whole UTC days. That is specific enough to distinguish it from content-reading siblings, reinforced by 'no content, handles or accounts', though it does not explicitly name an alternative.

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?

It gives an availability condition ('published only while the house switches it on; otherwise the answer is 404 not_published') and says no pass is needed, which helps an agent know whether it can call it. But it does not say when to prefer pulse over feed, status, boards, or other activity-related tools, so usage is only implied.

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