Skip to main content
Glama

Claude SEO Skills

claudeseoskills__get_ship_digest

Orient on this Ship — ALWAYS call this first. With no arguments it returns the section MAP and nothing else: every top-level section with its description and child_count, which is small and cheap even on a Ship of hundreds of nodes. Then pass { section_id } to list one section's direct children, and claudeseoskills__read_node for the ones worth reading. A large section arrives in pages — continue it 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_ship_digest"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo
section_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and it does disclose the important traits: the no-arg call returns the MAP 'and nothing else', that output is 'small and cheap even on a Ship of hundreds of nodes', and that large sections are paginated via cursor. Gaps remain around read-only semantics, behavior on an invalid section_id, and error/retry handling, but the core behavioral profile is communicated.

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 critical instruction ('ALWAYS call this first') is front-loaded, and the sentences are dense with actionable content rather than filler. Minor cost: the brace notation ({ section_id }, { cursor }) and clustered clauses make it slightly harder to scan than a clean ordered flow would be.

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 two-parameter read tool with no output schema and no annotations, this covers the essentials: what each mode returns, why the cheap map is preferred first, and how pagination works. It stops short of describing the full children record shape or error conditions, which is acceptable given the tool's narrow scope.

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 compensate and largely does: section_id is explained as selecting 'one section's direct children' and cursor as the paging continuation token for oversized sections. What is missing is any hint of the expected id format or whether cursor is scoped to a specific section_id.

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 uses a specific verb+resource framing ('Orient on this Ship') and precisely defines the two modes: a no-argument section MAP with 'every top-level section with its description and child_count', and a section_id mode listing 'direct children'. It explicitly routes detail-reading to claudeseoskills__read_node, though it never distinguishes itself from siblings like list_ship_nodes or get_blueprint_overview, which sound related.

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 gives an explicit call-order rule ('ALWAYS call this first'), states the no-argument case and what that returns, then the { section_id } case, then names the follow-up tool for actual reading. The continuation condition for paging ('A large section arrives in pages — continue it with { cursor }') is also spelled out, so an agent knows exactly which call to make next in every state.

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.