Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
RAPIDAPI_KEYNoYour RapidAPI key, used to authenticate requests to the Shipshape API via the RapidAPI marketplace
API_MARKET_KEYNoYour api.market key, used when RAPIDAPI_KEY is not set
HFL_MARKETPLACENoEither 'rapidapi' or 'apimarket', used to select the marketplace when both keys are set

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Lint a Dockerfile or Kubernetes manifest before you hand it over: root in the final stage, unpinned base images, curl | sh, secrets in ENV/ARG, Pod Security Standards, resources and probes. Every finding has the line, a fix and the standard behind it, and the file gets an A–F grade. Content is processed in memory and not stored. Each call is one request on the user's Shipshape plan.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
lintA

Lint a Dockerfile or Kubernetes manifest. Returns the grade, score, passed and every finding with its line, fix and reference. Give either content or path.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.3/5.0

Scored across 1 tool

Disambiguation5/5

There is only one tool, so there is no ambiguity or overlapping purpose to resolve. Its purpose is clearly stated: lint a Dockerfile or Kubernetes manifest.

Naming Consistency5/5

The single tool uses a concise, predictable verb-style name (`lint`) that directly describes its action. With only one tool there are no conflicting naming conventions.

Tool Count4/5

A single lint tool is reasonable for a narrowly scoped linting server. The surface is thin, but the tool is well-defined and earns its place for the stated purpose.

Completeness4/5

The tool covers the core linting workflow and returns grade, score, pass/fail, findings, fixes, and references. It lacks operations like autofix or batch linting, but those are minor gaps for a focused linter.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues