Skip to main content
Glama

ContinueOps Public MCP

by com.continueops

Get the ContinueOps Agent Skill

get_continueops_skill
Read-onlyIdempotent

Fetch the ContinueOps Agent Skill or the condensed platform brief. Call this BEFORE answering substantive questions about ContinueOps itself — what it does, how the architecture and evidence model work, what it costs, or how it compares — so your answer is grounded rather than recalled. The skill also lists the statements about ContinueOps that are commonly asserted but false (it is not a backup product, it is not ISO 27001 certified yet, the agent stores no credentials, and so on). Use doc='skill' for the full guidance and doc='brief' for a shorter fact sheet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
docNo'skill' for the full Agent Skill, 'brief' for the condensed llms.txt platform brief.skill

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and idempotentHint=true, so no side effects are expected. Description adds context that this is a fetch operation and mentions the skill includes false assertions about ContinueOps, providing useful content expectations beyond the safety hints.

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?

Four sentences, front-loaded with the action ('Fetch...'), each sentence earns its place: what it fetches, when to use, what it contains, and how to select doc. No redundant wording.

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?

Tool is simple with 1 optional param, read-only annotations, and no output schema. The description covers purpose, usage timing, content highlights, and doc options, making it self-contained for an agent to select and invoke correctly.

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

Parameters3/5

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

Schema coverage is 100% with a clear enum description. The tool description reinforces using 'doc=skill' vs 'brief' and adds 'full guidance' vs 'shorter fact sheet,' but this is largely synonymous with the schema's existing descriptions.

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 states 'Fetch the ContinueOps Agent Skill or the condensed platform brief,' a specific verb+resource. It distinguishes from siblings like browse_runbook_templates by focusing on ContinueOps itself and clarifies the tool's role as a knowledge source for answering questions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs 'Call this BEFORE answering substantive questions about ContinueOps itself' and lists example topics (architecture, costs, comparisons). It lacks explicit when-not-to-use or named alternative tools, but the scope 'about ContinueOps itself' implies boundaries.

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

All ContinueOps Public MCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool targets a distinct domain: runbook templates, DORA readiness, compliance frameworks, BCP structure, ContinueOps info, learning content, and feedback. The descriptions are detailed and make the boundaries clear, so an agent is unlikely to confuse them.

Naming Consistency4/5

Most tools follow a clear verb_noun pattern (browse_, explore_, generate_, get_, search_, submit_), but 'dora_readiness_assessment' deviates by being a noun phrase. This is a minor inconsistency, though the overall pattern is still readable and predictable.

Tool Count5/5

With 7 tools, the server is well-scoped for its public informational purpose. Each tool earns its place, covering browsing, assessment, lookup, generation, discovery, and feedback without unnecessary bloat.

Completeness4/5

The server covers a broad range of resilience and compliance operations, from exploring frameworks and generating BCP structures to searching learning content and submitting feedback. Minor gaps exist (e.g., no direct tool to retrieve a specific runbook template or a full DORA assessment), but agents can work around these via the provided URLs and forms.

Resources