Skip to main content
Glama
Sign In

GrowthDept

by app.growthdept
OverviewDiscussionsAdmin

What is happening

whats_happening
Read-onlyIdempotent

The last seven days for this business: what went out and where, how many decisions wait for the owner, and the one next step that only the owner can take. Start here.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare this as a safe, read-only, idempotent, closed-world summary. The description adds scope (seven days) and content categories (decisions, next step), but does not describe return format, freshness, or any limitations; with annotations carrying the safety profile, this is adequate but not rich.

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?

A single, front-loaded sentence that names the time window, the three summary elements, and the entry-point cue. Every clause adds useful information with no wasted wording.

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?

Given no parameters, no output schema, and rich annotations, the description provides enough to understand what the tool returns at a high level: a seven-day business summary, pending decisions, and a recommended next step. It could clarify what 'what went out' specifically covers, but the overall picture is complete for a dashboard-style read.

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 semantics to document. The baseline for zero-parameter tools is 4.

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 states a clear scope (last seven days for this business) and lists the summary contents: outgoing activity, pending decisions, and next owner action. It distinguishes itself as an entry point ('Start here') but leaves 'what went out and where' somewhat vague compared to sibling tools like activity or approvals_waiting.

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 directive 'Start here' provides explicit guidance to use this tool first, which is clear context for an entry-point summary tool. It does not name alternatives or exclusions, but the front-door role is unambiguous.

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

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