Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_payload_encode

Read-onlyIdempotent

Encodes text into base64, base64url, hex, URL, or form data for payload construction and safe transport in security testing.

Instructions

Encode text as base64, base64url, hex, URL, or form data.

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": {
      "data": "<data>",
      "encoding": "<encoding>"
    },
    "name": "oc_payload_encode"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYes
encodingYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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 and determinism profile is fully covered without the description. The description adds the set of supported encodings, which is modest but real behavioral information; it says nothing about output length, padding, or error behavior, but with strong annotation coverage a 3 is appropriate.

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?

A single short sentence, front-loaded with the verb and scoped by the format list. Nothing is padded or repeated.

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 explanation, and annotations cover the safety profile. What is missing is the exact vocabulary for the required 'encoding' argument, which for a two-required-parameter tool with 0% schema coverage is the key thing an agent needs.

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 description coverage is 0%, so the description must carry parameter meaning, and it only partially does: it implies 'data' is the text and 'encoding' selects a format by listing formats, but it never enumerates the exact accepted string values (e.g., whether it is 'url', 'urlencode', or 'form'). A caller still has to guess the literal token, which is the most failure-prone part of this API.

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?

The description gives a specific verb ('Encode') and resource ('text'), plus a concrete list of output formats (base64, base64url, hex, URL, form data), so an agent knows exactly what the tool produces. It stops short of naming any complementary sibling or distinguishing scope, so it lands at 4 rather than 5.

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 guidance on when to use this tool versus alternatives, no preconditions, and no note about a corresponding decode tool. The only implied usage is the trivial one baked into the verb 'encode', which is minimal.

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