Skip to main content
Glama

Stratalize Healthcare

Get Brand Momentum

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
  2. Removed
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Goes well past the annotations by disclosing the data source ('Stratalize brand index'), the return shape, and an explicit price point ('$0.02 USDC per call') — cost is behaviorally important for an agent deciding whether to call. With no output schema, the description does the job of describing returns, but leaves unstated what happens on an unknown brand (empty series vs. error) and whether cost is charged on failure.

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?

Front-loaded with the use case, then returns, then a concrete example, then source and price — a sensible order with no filler sentences. The example sentence is slightly long but earns its place by demonstrating the score/trend pairing.

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 one-parameter, read-only, no-output-schema tool, the definition covers what it does, when to call it, what comes back, where the data originates, and what it costs. The remaining gap is brand-name input semantics and failure behavior, which is minor relative to overall completeness.

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% for the single brand_name parameter, so the description must carry the burden, and it only does so implicitly via the 'HubSpot' example — suggesting a plain vendor name rather than a ticker or domain. It never states accepted formats, aliases, or whether ambiguous names resolve or fail.

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?

States a specific resource and measurement: 'vendor brand trajectory in AI recommendations', and enumerates what comes back ('4-week momentum score, trend direction, and weekly movement series'). This is clearly distinct from benchmark-style siblings like get_citation_authority or get_category_ai_leaders, though it never names an alternative to contrast against.

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?

Gives two concrete triggering scenarios ('monitoring a vendor brand trajectory' and 'tracking week-over-week competitor momentum for a CMO brief'), which is enough for an agent to decide relevance. It stops short of exclusions or pointing at a sibling when the question is, say, category-level rather than brand-level.

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