Skip to main content
Glama

get_brand_momentum

Read-only

Use when monitoring a vendor brand trajectory in AI recommendations or tracking week-over-week competitor momentum for a CMO brief. Returns 4-week momentum score, trend direction, and weekly movement series. Example: HubSpot 4-week momentum +1.8, GROWING trend — 3 consecutive weeks of citation increase following major product launch — competitive signal requiring CMO attention. Source: Stratalize brand index. $0.02 USDC per call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "brand_name": "<brand_name>"
    },
    "name": "get_brand_momentum"
  }
}

Input Schema

NameRequiredDescriptionDefault
brand_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, open-world), so the description's job is supplementary — and it delivers things the annotations cannot: the data source ('Stratalize brand index') and a per-call price ('$0.02 USDC per call'), which matters for a metered tool. It says nothing about rate limits, freshness lag beyond the 4-week window, or failure behavior for unknown brands.

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 definition is front-loaded with the 'Use when' trigger, then return shape, then a concrete example, then source and price — a sensible order with little waste. The illustrative example is somewhat verbose (recounting '3 consecutive weeks of citation increase following major product launch') and could be trimmed without losing signal.

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?

With no output schema, the description carries the burden of describing returns and does so explicitly (momentum score, trend direction, weekly series), plus source and cost. For a one-parameter read-only lookup that is close to complete; only input format expectations for brand_name remain unspecified.

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 0% and no description text explains the single parameter directly, so the agent relies on the schema's bare 'brand_name' string. The worked example ('HubSpot 4-week momentum +1.8') implicitly shows that a recognizable vendor/brand name is the expected input, which is modest added meaning but not a substitute for documenting accepted forms.

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 uses a specific verb-plus-resource framing ('Returns 4-week momentum score, trend direction, and weekly movement series' about a vendor brand trajectory in AI recommendations), which is far more than a restatement of the name. It does not name or contrast any of the many sibling tools, so the agent must infer that this is the brand-trajectory tool rather than, say, get_category_ai_leaders or get_citation_authority.

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?

Two concrete use contexts are given ('monitoring a vendor brand trajectory in AI recommendations' and 'tracking week-over-week competitor momentum for a CMO brief'), which is enough for an agent to match an intent. There are no explicit exclusions or named alternatives, so routing away from similar category/citation tools is left to inference.

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