Skip to main content
Glama
Sign In
keyword-steroids-gold

keyword-steroids-gold

by MaximKonovalovDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

gold_setup_check

Run this first to verify your Keyword Steroids Gold configuration: view license tier, see which API keys are missing, and get the exact next step.

Instructions

SETUP CHECK for Keyword Steroids Gold — run this FIRST. Shows license tier, which API keys are set vs missing (names only, never values), and the exact next step.

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": "gold_setup_check"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.9/5.0
Behavior5/5

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

Given no annotations, the description carries full behavioral burden. It discloses the tool is a check (non-mutating), what it reveals (license tier, API key presence, next step), and a critical security behavior: 'names only, never values'. This is highly transparent for a zero-parameter operation.

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?

Two sentences, front-loaded with the operation name and urgency ('run this FIRST'). Every element is purposeful, with no filler. The structure immediately conveys priority and content.

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

Completeness5/5

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

For a zero-parameter tool with no output schema, the description sufficiently explains inputs (none needed), outputs (license tier, API key status, next step), and usage context (first step before keyword operations). Nothing important is missing.

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?

With zero parameters, the schema needs no elaboration. The description adds no parameter-specific details because none exist, but it does clarify the tool's output context, which is more than the baseline for a param-less tool.

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?

Description names a specific verb-resource pair ('SETUP CHECK') and a precise purpose: shows license tier, API key status, and next step. It clearly separates itself from the keyword-focused sibling tools by establishing itself as the diagnostic first-run check.

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?

Explicitly instructs the agent to 'run this FIRST', which is a direct usage guideline. It also implies it should precede any keyword or crawl operations, and the phrase 'exact next step' signals the tool's role in guiding subsequent actions.

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

Deploy Server

Other Tools