Skip to main content
Glama
Sign In
Simplepush MCP Server

Simplepush MCP Server

Official
by simplepush
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Everything going on for a member (or the whole organization)

get_activity

Summarize recent organization or member activity: open, declined, expired tasks, answers, replies, cancellations, submissions with who and when. Optional start date (default 7 days).

Instructions

Use this first for 'any problems with ?', 'what is going on with / at the site?', 'catch me up', 'anything I should know?'. One call returns the bundle: open tasks, tasks that were declined or expired, and the window's answers, replies, declines, cancellations and ad-hoc submissions — with who and when. Defaults to the last 7 days. Omit member for the whole organization.

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
sinceNoISO-8601 instant; default is 7 days ago.
memberNoMember name or usr_ id. Omit for the whole organization.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well. It discloses the default 7-day window, the specific categories included (open/declined/expired tasks, answers, replies, declines, cancellations, ad-hoc submissions), and the org-vs-member scoping behavior. This goes well beyond a generic 'returns activity' statement.

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?

Three sentences, with the most important guidance front-loaded ('Use this first'). Every sentence adds value: example intents, returned bundle, default window, and scoping rule. No filler or redundancy.

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?

There is no output schema, so the description appropriately explains the return contents: tasks, answers, replies, declines, cancellations, and ad-hoc submissions with who and when. Combined with default behavior and member omission semantics, an agent has enough to invoke the tool correctly without further inference.

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 description coverage is 100%, so the baseline is 3. The description's 'Defaults to the last 7 days' and 'Omit member for the whole organization' restate what the schema already documents rather than adding meaning beyond it.

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?

The description clearly states a broad, catch-all purpose ('Use this first') and enumerates the exact intents it covers, from 'any problems with <member>?' to 'anything I should know?'. It also spells out the bundled resource types returned, which distinguishes it from targeted siblings like query_tasks or get_task.

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 description gives explicit when-to-use guidance with concrete example questions and explicitly says to omit member for the whole organization. It does not name specific sibling alternatives or state when not to use it, but 'Use this first' clearly communicates priority among the broader toolset.

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

Deploy Server

Other Tools