Skip to main content
Glama

Encode OID BER content octets

bpj_oid_ber_content
Read-onlyIdempotent

Encode a dotted ASN.1 object identifier into BER value octets, excluding tag and length.

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": {
      "value": "<value>"
    },
    "name": "bpj_oid_ber_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior. The description adds the useful output boundary (value octets only, no tag/length), but does not disclose error behavior for malformed OIDs or how the resulting octets are represented to the caller.

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?

One tight sentence with the output boundary front-loaded and no filler. Every phrase contributes to understanding the input or output.

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?

For a simple pure encoding tool, the description covers the input type and the output scope, and annotations cover safety. But with no output schema, it should more clearly state how the BER octets are returned, for example as a hex string or byte array, and what happens on invalid OIDs.

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

Parameters4/5

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

Schema coverage is 0%, and the schema only labels the single parameter as 'Input value' with a maxLength. The description compensates by defining it as a dotted ASN.1 object identifier, which is the key semantic an agent needs; it stops short of giving format examples or validation constraints.

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 ('Encode') and names both the input ('dotted ASN.1 object identifier') and the output ('BER value octets'), including the important boundary that tag and length are excluded. This is enough to distinguish it from a full BER/TLV encoder without relying on the title.

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?

It implicitly scopes the tool to producing content octets only by excluding tag and length, which hints at when a caller would choose it. However, it does not explicitly state when to use it versus a full BER encoder or a decoder, and no alternative tool is named.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.