Skip to main content
Glama

security-crypto

saml_assertion_decode

Decode Base64 / URL-encoded / Deflate SAML 2.0 AuthnRequests or Responses and extract Issuer, NameID, Audience, and validity timestamps.

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

Input Schema

NameRequiredDescriptionDefault
textNoSAMLRequest/SAMLResponse base64 or raw XML.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden. It does disclose accepted encodings (Base64, URL-encoded, Deflate) and the extracted fields, which is useful. But it never says whether signatures are validated or merely ignored, whether the operation is purely local/offline, or what happens on malformed input — critical for a security-inspection tool where an agent might mistake decoding for verification.

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 sentence, front-loaded with the verb and accepted input formats, followed immediately by the extracted outputs. No filler or redundancy.

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?

The description usefully compensates for the absent output schema by naming the returned fields. However, for a security-adjacent decoding tool with no annotations, the missing statement about signature validation and local vs remote processing leaves a real gap an agent would care about.

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 coverage is 100% with a single well-described parameter, so the schema does the heavy lifting. The description adds modest value by widening the accepted forms beyond the schema's 'base64 or raw XML' to include URL-encoded and Deflate payloads, but adds no detail on how to obtain or format the value.

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?

Specific verb (decode) plus specific resource (SAML 2.0 AuthnRequests/Responses) and an enumeration of what gets extracted (Issuer, NameID, Audience, timestamps). The SAML framing inherently separates it from jwt_decode_and_audit, though it never explicitly contrasts with siblings.

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?

Usage is only implied by the resource named — an agent can infer this is for inspecting SAML assertions during SSO/debugging work. There is no explicit when-to-use statement, no prerequisites, and no note about when a different tool (e.g. JWT or X.509 inspection) would be the right choice.

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