Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
RAPIDAPI_KEYNoYour RapidAPI key for the Specwise API.
API_MARKET_KEYNoYour api.market key, used when RAPIDAPI_KEY is not set.
HFL_MARKETPLACENoWhich marketplace to use when both keys are set: 'rapidapi' or 'apimarket'.

Instructions

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

Validate an OpenAPI (3.x or Swagger 2.0) document and get every error with its JSON Pointer, line and column. Compare two OpenAPI 3.x versions and get each change classified as breaking, warning, non-breaking or info, with a semver suggestion; use it after editing a spec, against the git version. Validate JSON Schemas and data. Documents are processed in memory and not stored, and external $refs are never fetched. Each call is one request on the user's Specwise 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
validate_openapiA

Validate an OpenAPI 3.0/3.1/3.2 or Swagger 2.0 document. Returns every error (not just the first) with its JSON Pointer, line and column, plus lint warnings.

diff_openapiA

Compare two OpenAPI 3.x documents. Each change is breaking, warning, non-breaking or info; breaking says whether any is breaking, and semver suggests the version bump.

Typical use after editing a spec: revision_path="openapi.yaml", base_git_ref="main".

validate_json_schemaA

Check a JSON Schema against its meta-schema and, if given, validate data against it. Every error has the instance path, the schema path and, for text input, the line.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 3 tools

Disambiguation5/5

Each tool targets a clearly distinct operation: validation of OpenAPI, diffing of OpenAPI, and JSON Schema validation. While validate_openapi and validate_json_schema both validate, the domains (OpenAPI document vs. JSON Schema + data) are explicitly separated, leaving no realistic ambiguity.

Naming Consistency5/5

All three tools follow a strict verb_object pattern: validate_openapi, diff_openapi, validate_json_schema. Predictable and consistent throughout.

Tool Count4/5

Three tools is slightly thin for a spec-tooling server, but each is a distinct, well-scoped capability with no filler. A 3-tool set is on the low edge of the ideal band but defensible for a focused lint/diff utility.

Completeness4/5

The core spec lifecycle for validation and comparison is covered, including breaking-change detection and semver suggestions. Gaps exist around formatting/bundling or schema conversion, but agents can work around these; the surface is coherent for a focused toolset.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues