Skip to main content
Glama

BRAINIAC Content & Keyword Analytics

Keyword opportunity score

seo-content_keyword-opportunity-score
Read-onlyIdempotent

Rank keywords by click upside to a target position, weighted by difficulty using a disclosed formula. Price $0.03 USDC. POST /api/v1/seo-content/keyword-opportunity-score. 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": {
      "ctrCurve": "<ctrCurve>",
      "keywords": "<keywords>"
    },
    "name": "seo-content_keyword-opportunity-score"
  }
}

Input Schema

NameRequiredDescriptionDefault
ctrCurveYesctrCurve, array. Required.
keywordsYeskeywords, array. Required.
targetPositionNotargetPosition, integer, from 1 to 9007199254740991. Required.
difficultyWeightNodifficultyWeight, number, from 0 to any. Required.

Output Schema

NameRequiredDescriptionDefault
rankedNoranked. Array.
formulaNoformula. String.
sourcesNosources. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing a concrete price ($0.03 USDC), the x402 payment gate, and the important behavioral fact that unpaid invocations do not execute the scoring. It also notes the formula is 'disclosed,' signaling the output is explainable. Annotations already cover read-only/idempotent safety, so this added cost and execution-gating context is high-value.

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?

Three short sentences, front-loaded with the core function, then price, then the endpoint and payment behavior. No filler; each sentence carries distinct operational information.

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 annotations, a full schema, and an output schema, the description covers the remaining burdens: cost, payment flow, and non-execution on unpaid calls. Minor gap: it does not indicate whether the ctrCurve array must align in length with keywords, though the schema bounds each element.

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 all four parameters and their constraints. The description adds conceptual linkage ('target position', 'weighted by difficulty') that hints at how targetPosition and difficultyWeight interact, but it does not explain ctrCurve or the shape of keyword entries beyond what the schema states.

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 verb and resource: 'Rank keywords by click upside to a target position, weighted by difficulty.' The scoring method (click upside, difficulty weighting) is concrete enough to separate it from siblings like keyword-difficulty-estimate, but no sibling is named, so differentiation is inferred rather than stated.

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

Usage Guidelines3/5

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

Usage is implied by the ranking purpose, and there is one real precondition disclosed: an unpaid call returns x402 payment terms and does not run. However, there is no explicit when-to-use/when-not guidance and no routing to alternative sibling tools for related scoring tasks.

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