Skip to main content
Glama

BRAINIAC Content & Keyword Analytics

Content decay Mann-Kendall test

seo-content_content-decay-detect
Read-onlyIdempotent

Flag pages whose clicks or impressions show a statistically significant decline with Mann-Kendall, Sen slope and windowed percent change. Price $0.03 USDC. POST /api/v1/seo-content/content-decay-detect. An unpaid call returns the x402 payment terms and does not run.

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": {
      "series": "<series>"
    },
    "name": "seo-content_content-decay-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
alphaNoalpha, number, from any to 0.5. Required.
periodNoperiod, value. Optional.
seriesYesseries, array. Required.
minDropPctNominDropPct, number, from 0 to any. Required.
comparisonWindowNocomparisonWindow, integer, from 1 to 9007199254740991. Required.

Output Schema

NameRequiredDescriptionDefault
resultsNoresults. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description goes meaningfully beyond them by disclosing cost ($0.03 USDC), the transport (POST /api/v1/...), and the critical quirk that an unpaid call returns x402 payment terms without executing. It does not mention minimum series length, error conditions, or how significance/minDropPct interact, leaving some behavioral gaps.

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?

Three tight sentences with the purpose front-loaded and no wasted wording; pricing, endpoint, and payment fallback follow in a logical order. The endpoint string is somewhat boilerplate but is functional information for an x402 tool.

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 a full output schema and complete annotation coverage, the description only needs to supply purpose, cost, and invocation behavior, and it does all three. Minor omissions are expectations around input series (minimum length, ordering) and the meaning of a 'decline' relative to minDropPct, but these are secondary given the rich schema.

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 schema already documents alpha, period, minDropPct, comparisonWindow, and the series array. The description only hints at parameter meaning indirectly through "statistically significant" (alpha) and "windowed percent change" (comparisonWindow) and adds no syntax, ranges, or defaults beyond the schema, so the baseline of 3 applies.

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 gives a specific verb and outcome ("Flag pages whose clicks or impressions show a statistically significant decline") plus the methods used (Mann-Kendall, Sen slope, windowed percent change), which clearly separates it from siblings like rank-change-summary or opportunity-score. It stops short of explicitly contrasting itself with any named sibling, so it is clear but not fully differentiated.

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

Usage Guidelines2/5

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

It implies the applicable scenario (you have per-URL click/impression series) but never states when to choose this over seo-content_rank-change-summary or another trend tool, nor any preconditions or when-not-to-use cases. The only guidance-like content concerns payment and transport, not tool selection.

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