asn1-mcp

compile_asn1_schema

Compiles ASN.1 schema definitions into executable source code. Use this tool whenever a user asks to generate code, compile an ASN.1 schema, or create a codec (e.g., DER, PER, UPER, BER) for a specific programming language. The tool returns the compilation status, error messages, and files containing the generated source code.

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

Input Schema

Name	Required	Description	Default
`codec`	No	The ASN.1 encoding rules to support in the generated code. Valid options include 'uper', 'per', 'der', 'ber', or 'oer'. If the user does not specify a codec, default to 'der'.	der
`userId`	No	The user's email address to look up the asn1.io user account. If the user's identity is unknown, pass an empty string.
`fileName`	No	The name of the schema file being compiled. This should end in '.asn' (e.g., 'Rocket.asn'). If the user does not provide a filename, invent a logical one based on the schema's main module name. It is used for errors to reference a specific location in the schema .	schema.asn
`schemaContent`	No	Plain-text ASN.1 schema definition. This must be valid ASN.1 syntax, typically starting with the 'DEFINITIONS' keyword and concluding with 'END'.
`targetLanguage`	No	The target programming language for the generated code. Allowed values include 'python' and ‘rust’. Infer this from the user's prompt. If not specified, ask the user before calling the tool.	python

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description usefully discloses the return payload (compilation status, error messages, generated source files), which is real behavioral value. It omits operational traits: whether compilation happens remotely, whether an asn1.io account/user identity is required (implied by userId), failure behavior, or side effects like files being persisted.

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?

Three sentences, front-loaded with the core action, then triggers, then return shape. No filler or restated title; every sentence carries information.

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

Completeness4/5

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

For a 5-parameter tool with no annotations and no output schema, the description covers both inputs (via the fully documented schema) and outputs (status, errors, files). The remaining gap is the operational context around the asn1.io account and how generated files are delivered.

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 100%, so every parameter including codec defaults, fileName conventions, and targetLanguage values is already documented. The description adds no parameter meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb ('Compiles') and resource ('ASN.1 schema definitions into executable source code'), and enumerates the codec families (DER, PER, UPER, BER). An agent can immediately tell what the tool produces without opening the schema.

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?

Explicitly lists the triggering user requests (generate code, compile an ASN.1 schema, create a codec), which is clear context for when to call. There are no sibling tools and no when-not-to-use cases, so it stops short of a 5.

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

All asn1-mcp tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?