Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_recommend_tools

Read-onlyIdempotent

Recommends OpenCyber tools by matching a stated objective and target type through deterministic criteria, helping users select relevant security tools for authorized engagements.

Instructions

Recommend OpenCyber tools using deterministic objective matching.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "objective": "<objective>"
    },
    "name": "oc_recommend_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
objectiveYes
target_typeNoweb

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The phrase 'deterministic objective matching' adds genuinely useful context — results are reproducible and rule-based rather than heuristic — but nothing is said about how many tools are returned, whether ranking/confidence is included, or whether unknown objectives yield empty results.

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?

A single front-loaded sentence with zero filler and no redundancy. It is arguably too terse rather than bloated, but the size itself is appropriate for the dimension.

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 explained, but for a two-parameter tool with no parameter documentation the description should at minimum define the objective string and the target_type domain. As written, an agent cannot confidently construct a call or predict whether the recommendation set is exhaustive or ranked.

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% for two parameters, so the description must carry the load and does not: 'objective' (required) gets no format, granularity, or example, and 'target_type' (default 'web') is never mentioned at all, leaving its vocabulary entirely unknown. The only hint is the word 'objective' appearing inside the mechanism phrase.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ('Recommend') and resource ('OpenCyber tools') and even the matching mechanism ('deterministic objective matching'), so the basic operation is identifiable. However, it never clarifies scope or how this meta-tool relates to the sibling tools it recommends, and 'objective' is left undefined, so the purpose is only vaguely bounded.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no when-not-to-use guidance, and no mention of any alternative workflow (e.g., browsing the tool catalog directly). The agent must infer from the name alone that this is a discovery/routing helper to call before picking a concrete oc_* tool.

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