Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

webdev_openapi_viewer

Read-onlyIdempotent

Parse an OpenAPI or Swagger specification to detect its version, count endpoints, and list component schemas. Use it to inspect or summarize an API contract from text.

Instructions

OpenAPI/Swagger Spec Parser And Summarizer. Parse a pasted OpenAPI or Swagger API specification (JSON, or a simple subset of YAML) and return its detected version, total operation count, and component/definition schemas. Use it to inspect or summarize an API contract you already have as text; use format_json_schema_generator instead to derive a JSON Schema from sample data, or format_json to pretty-print generic JSON. Does not fetch any URL — it only parses the string you send; pure local compute, read-only, non-destructive, contacts no external service, and is rate-limited (30 requests/min anonymous). Returns the normalized spec object, a version label, the endpoint count, and the schemas map.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
specificationYesRaw OpenAPI/Swagger document as text (aliases: spec, input). Parsed as JSON first, then as simple YAML if that fails. Must be non-empty and contain an "openapi" or "swagger" field plus an "info" object, or the request is rejected.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
specNoThe normalized specification object parsed from the input.
versionNoDetected version label, e.g. "OpenAPI 3.0.0", "Swagger 2.0", or "Unknown".
endpointCountNoTotal number of HTTP operations (get/post/put/delete/patch/options/head) across all paths.
schemasNoComponent schemas (OpenAPI components.schemas) or Swagger definitions; empty object if none.
Behavior5/5

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint, openWorldHint. Description adds: 'pure local compute, read-only, non-destructive, contacts no external service, rate-limited (30 req/min)'. This enriches transparency beyond annotations without contradiction.

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?

Description is well-structured: starts with main purpose, then usage guidance, then behavioral notes. Every sentence adds value; no fluff. It is front-loaded and efficient.

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?

Given single parameter, rich annotations, and output schema (mentioned), description covers input, behavior, constraints, rate limiting, and return values (normalized spec, version, endpoint count, schemas map). Highly complete.

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

Parameters5/5

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

Schema coverage is 100% with detailed parameter description. Description adds parsing details (JSON first then simple YAML) and validation (must contain openapi/swagger and info). This provides significant meaning beyond the schema.

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 clearly states 'OpenAPI/Swagger Spec Parser And Summarizer' and explains what it does: parse spec and return version, operation count, and schemas. It distinguishes from siblings like format_json_schema_generator and format_json.

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 states when to use this tool ('inspect or summarize an API contract you have as text') and when to use alternatives ('use format_json_schema_generator instead to derive a JSON Schema from sample data, or format_json to pretty-print generic JSON'). Also clarifies does not fetch URLs.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server