Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_poc_render

Renders a PoC spec into a bounded, stdlib-only Python verifier for an engagement, or stores custom source for approval; returns code path and SHA-256 without executing.

Instructions

Render a PoC spec into a bounded stdlib-only Python verifier under the engagement, or store custom source verbatim for the separate approval tier. Returns the code path and SHA-256 bound by the run approval; does not execute anything.

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": {
      "engagement_id": "<engagement_id>",
      "spec_id": "<spec_id>"
    },
    "name": "oc_poc_render"
  }
}

Input Schema

NameRequiredDescriptionDefault
spec_idYes
engagement_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations only declare readOnly=false, idempotent=false, destructive=false; the description adds real substance beyond them: the generated code is 'bounded stdlib-only', the tool performs no execution, and the returned SHA-256 is bound by the run approval. The unexplained 'separate approval tier' and the lack of any note on regeneration/overwrite behavior keep it 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?

Two dense sentences with the core action and the no-execution guarantee front-loaded; little waste. The second sentence is packed with caveats ('bounded stdlib-only', 'verbatim', 'separate approval tier') that could have been split for readability.

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

Completeness3/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 no elaboration, and the description does name the key outputs. However, the 'store custom source verbatim' mode has no corresponding input in the two-parameter schema, and the approval-tier mechanics are referenced but never explained, leaving an agent unsure how to trigger or satisfy that path.

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%, so the description carries the full burden for both parameters. 'Under the engagement' loosely implies engagement_id scoping and 'a PoC spec' implies spec_id, but neither is defined, nor is any format or validation rule given; the custom-source mode even lacks a visible source parameter.

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

Purpose4/5

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

Names a specific verb (render/store) and resource (PoC spec into a bounded stdlib-only Python verifier), plus the concrete output (code path and SHA-256). The clause 'does not execute anything' implicitly separates it from siblings like oc_poc_run and oc_poc_lint, though no sibling is named explicitly.

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

Usage Guidelines3/5

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

Two modes are described ('render a spec' vs 'store custom source verbatim for the separate approval tier'), which implies when each applies, but the description never states the condition for choosing one over the other or when to prefer oc_poc_run/oc_poc_lint instead. Usage is inferable rather than spelled out.

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