Skip to main content
Glama

Claude SEO Skills

claudeseoskills__get_blueprint_overview

Read the human-AUTHORED overview prose for the Ship (omit node_id) or for one section. Useful only where someone has written a summary; it is not the way to navigate — claudeseoskills__get_ship_digest is the map, call that first. When no summary has been written this falls back to the same section map claudeseoskills__get_ship_digest returns, drilled with { section_id } and paged with { cursor }.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "claudeseoskills__get_blueprint_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo
node_idNo
section_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are supplied, so the description must carry the behavioral burden. It does disclose an important non-obvious trait: when no summary has been written, the tool falls back to the section map that get_ship_digest returns, with section_id drilling and cursor paging. It does not cover permissions or the exact return shape, which keeps it short of a 5.

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 text is dense, but the guidance is front-loaded: the purpose comes first, then the routing rule, then the fallback behavior. Every sentence adds operative information, though the last sentence packs three ideas (fallback, drilling, paging) into one long clause.

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 read-only tool that has zero annotations, zero schema coverage, and no output schema, the description covers the purpose, the routing, the fallback, and all three parameters. Only the return shape and permission requirements are unstated, which is a minor gap given that this is a prose-reading tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain the three parameters itself. It does: omit node_id for ship-level overview, pass a section_id to target one section, and use cursor to page through results. That is meaningful compensation, though it does not say what a node_id value selects relative to section_id.

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 gives a specific verb and resource: 'Read the human-AUTHORED overview prose for the Ship (omit node_id) or for one section.' It also explicitly distinguishes this tool from the sibling get_ship_digest by calling that one 'the map,' so an agent can tell the two apart without opening either schema.

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

Usage Guidelines5/5

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

It states both when it is useful ('Useful only where someone has written a summary') and when it is not ('it is not the way to navigate'), and it then names the alternative: 'claudeseoskills__get_ship_digest is the map, call that first.' That is an explicit when/when-not/alternative rule.

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.