Skip to main content
Glama

security-crypto

pgp_packet_inspect

Parse ASCII-armored OpenPGP public/private keys or signatures to decode RFC-4880 packet tags, RSA/EdDSA versions, CRC24 armor checksum, and User IDs.

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

Input Schema

NameRequiredDescriptionDefault
textNo
filePathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the safety and behavioral burden. It implies a read-only parse operation and lists decoded fields, but does not state whether private key material is handled specially, whether validation occurs, or what errors may arise.

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?

The description is a single front-loaded sentence with no wasted wording. It is dense but efficient, though a little more structure could improve scanability.

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?

For a parser with no annotations, no output schema, and undocumented parameters, the description is under-specified. It explains the general purpose but does not cover input selection, return shape, error behavior, or handling of private key material.

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 should explain the two parameters. It indicates the input should be ASCII-armored OpenPGP data, but does not clarify the meaning or precedence of text versus filePath.

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 and resource: parse ASCII-armored OpenPGP keys or signatures to decode packet tags, versions, CRC24 checksum, and User IDs. The OpenPGP scope clearly differentiates it from certificate, SSH, and JWT inspection siblings, though it does not explicitly name alternatives.

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?

It implies the tool is for decoding armored OpenPGP data, but there is no explicit guidance on when to use it versus alternatives, when not to use it, or whether text versus filePath input is preferred.

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.

Resources