Skip to main content
Glama

BRAINIAC SOAP Security

Score SOAP policy strength

soap-security_policy-strength
Read-onlyIdempotent

Score a caller-supplied algorithm suite, body signature, body encryption, timestamp, and token kind. Basic256Sha256 contributes the most, TripleDes and None the least. A username token scores below an X.509 token. The grade follows that score. No certificate is validated and no policy file is fetched. Price $0.04 USDC. POST /api/v1/soap-security/policy-strength. An unpaid call returns the x402 payment terms and does not run.

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": {
      "algorithm_suite": "<algorithm_suite>",
      "body_signed": "<body_signed>",
      "body_encrypted": "<body_encrypted>",
      "timestamp": "<timestamp>",
      "token": "<token>"
    },
    "name": "soap-security_policy-strength"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYestoken, string, one of x509, username, none. Required.
timestampYestimestamp, boolean. Required.
body_signedYesbody signed, boolean. Required.
body_encryptedYesbody encrypted, boolean. Required.
algorithm_suiteYesalgorithm suite, string, one of Basic256Sha256, Basic256, Basic128Sha256, Basic128, TripleDes, None. Required.

Output Schema

NameRequiredDescriptionDefault
security_policy_gradeNosecurity_policy_grade. String.
cryptographic_strength_scoreNocryptographic_strength_score. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description adds genuinely non-obvious context: nothing is fetched or validated, the call costs $0.04 USDC, and an unpaid call returns x402 payment terms without executing. That payment-gate behavior is the kind of detail an agent cannot get from structured fields.

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?

Six short sentences, all front-loaded with the scoring semantics first and operational details (price, endpoint, payment gate) last. Dense but every sentence carries information; the price/endpoint line is the most mechanical but is still operationally necessary.

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?

With five required enum/boolean parameters, an output schema for the grade, and annotations covering safety, the description covers what remains: scoring direction, absence of external lookups, and payment failure behavior. Nothing essential for a correct call appears missing.

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 100% with enums documented, so the baseline is 3; the description exceeds it by supplying the relative weighting ('Basic256Sha256 contributes the most, TripleDes and None the least' and username below x509), which tells the agent how values affect the grade rather than just what values are legal.

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?

Opens with a specific verb and resource (score a SOAP policy) and enumerates the exact inputs being graded, so an agent knows precisely what the tool evaluates. It does not name the sibling audit tool, so differentiation is left implicit rather than stated.

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?

The line 'No certificate is validated and no policy file is fetched' implicitly separates this from a fetching audit tool and tells the agent the caller must supply the policy facts. However, it never explicitly says when to choose this over soap-security_soap-security-policy-audit, leaving the routing inference to the agent.

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