Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_catalog

Read-onlyIdempotent

Search OpenCyber executables and native MCP tools by exact oc_* name, substring query, or category, and compare shipped versus advertised catalog digests to confirm release consistency.

Instructions

Search every OpenCyber executable and native MCP tool by exact oc_* name, substring query, or category. Also reports the catalog digest: recorded_catalog_digest is the contract this release shipped, catalog_digest is what this process advertises, and catalog_matches_release says whether they agree. An unfiltered call returns only counts; set include_all=true only when the complete catalog is genuinely required.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
limitNo
queryNo
offsetNo
categoryNo
include_allNo
missing_onlyNo
registered_onlyNo
include_contractsNo
expected_catalog_digestNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real behavioral detail beyond that: an unfiltered call yields only counts, and it explains what the three digest fields mean (recorded_catalog_digest as the shipped contract, catalog_digest as what this process advertises, catalog_matches_release as their agreement). It does not describe pagination or ordering behavior, so it stops short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the search capability, then the digest semantics, then the include_all caution — no filler or restatement of the name. The middle sentence is dense with three field names, but each carries information an agent cannot get from the schema.

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

Completeness2/5

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

An output schema exists, so return values need not be re-explained, and the annotations cover safety. However, for a 10-parameter tool with zero schema description coverage, leaving six parameters (including expected_catalog_digest, missing_only, and registered_only) undocumented makes the definition insufficient for reliable invocation.

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

Parameters2/5

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

Schema description coverage is 0% across 10 parameters, so the description must carry the burden, yet it only glosses name, query, category, and include_all and never mentions limit, offset, missing_only, registered_only, include_contracts, or expected_catalog_digest. An agent must guess at the semantics of the majority of the inputs, including the digest-comparison parameter that the description's own digest discussion implies.

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?

The description uses a specific verb (Search) and a precisely bounded resource (every OpenCyber executable and native MCP tool), and names the three lookup modes (exact `oc_*` name, substring query, category). It also declares the secondary purpose of digest reporting, so an agent knows this tool is the catalog/index rather than any individual sibling tool like oc_amass or oc_bash.

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?

It gives a concrete default behavior ('An unfiltered call returns only counts') plus an explicit when-not rule: set include_all=true only when the complete catalog is genuinely required. What is missing is guidance on choosing between name, query, and category filters, or on combining them with limit/offset.

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