Skip to main content
Glama

Momentum across competitors

get_momentum
Read-only

Momentum for every tracked competitor at once, ranked: label (Heating up, Steady, Cooling or Gone quiet), score and confidence, plus this account's own momentum built from its NPS trend and win-rate trend. Use it to compare competitors or answer 'who is heating up fastest?'. For the drivers and recent signals behind one competitor use get_competitor; for what changed this week use get_briefing. Read-only, no parameters. A competitor with too little data is labeled as such, not guessed.

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_momentum"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and no params are taken, so safety is covered; the description still adds real behavior beyond them by naming the ranking output shape, the four label values, and the insufficient-data case ('labeled as such, not guessed'). It does not explain ordering ties or how momentum is computed for competitors, which keeps it short of a 5.

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?

Four tight sentences, front-loaded with what the tool returns, then the use case, then the sibling routing, then the read-only/no-param caveat. No sentence is redundant or restates the title.

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 correctly spends its words describing the return payload (label set, score, confidence, account momentum) and the null/low-data behavior. For a parameterless read tool, nothing an agent needs before calling it is missing.

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?

Zero parameters means there is nothing for the description to disambiguate, and it helpfully confirms 'no parameters' so the agent does not hunt for filters. Baseline for a parameterless tool applies cleanly.

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 ('momentum for every tracked competitor at once, ranked') and enumerates the returned facets: label, score, confidence, plus the account's own NPS/win-rate-derived momentum. It is unmistakably distinct from get_competitor, which is scoped to one competitor's drivers.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives positive triggers ('compare competitors', 'who is heating up fastest?') and two explicit alternative routes with their conditions: get_competitor for drivers/recent signals behind one competitor, get_briefing for what changed this week. No inference is required to pick the right tool.

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.