SEOctopus

Overview Schema Source Related Servers Discussions Admin

octo_score

Calculate a weighted OctoScore (0-100) for any URL using Google ranking factors, returning a letter grade and actionable recommendations.

Instructions

Calculate the OctoScore (0-100) - weighted by Google ranking factors with letter grade and action items

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": {
      "url": "<url>"
    },
    "name": "octo_score"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	URL to score
`keyword`	No	Target keyword for relevance scoring
`propertyId`	No	GA4 property ID for engagement data
`siteUrl`	No	GSC property URL for keyword data

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 21, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations, the description partially explains behavior: it calculates a score and returns a grade/actions. However, it does not disclose side effects (likely none), required permissions, rate limits, or how optional parameters like propertyId affect behavior. The mention of 'weighted by Google ranking factors' adds context but omits specifics.

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 description is a single sentence that conveys essential information (verb, resource, output details). It is concise without being overly terse, though it could be improved by front-loading the verb more explicitly and adding a brief usage note.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, no annotations, and 4 parameters (3 optional), the description should explain the return format (e.g., structure of letter grade and action items) and prerequisites. It fails to do so, leaving the agent with insufficient information to invoke the tool correctly in complex scenarios.

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 baseline is 3. The description adds no additional meaning beyond what the schema already provides; for example, it doesn't clarify how 'keyword' influences relevance scoring or when 'siteUrl' is necessary. It merely echoes the fact that these parameters exist.

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?

The description clearly identifies the tool's purpose: to calculate an OctoScore on a 0-100 scale, weighted by Google ranking factors, and produce a letter grade and action items. It specifies the verb 'Calculate' and the resource 'OctoScore', making it distinct from sibling tools that focus on analytics, audits, or rankings.

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?

No guidance is provided on when to use this tool versus alternatives such as rank_check or audit_page. The description does not include any 'when-to-use' or 'when-not-to-use' information, forcing the agent to infer based on name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.