Skip to main content
Glama

Audit WSDL and XSD dependencies

soap-contracts_wsdl-xsd-dependency-audit
Read-onlyIdempotent

Compare a caller-supplied WSDL 1.1 document and its XSD documents, including an optional previous set. audit_status is valid, warnings, breaking_changes, invalid, or incomplete. Imports are not downloaded. A schema difference is syntactic and is not proof that a SOAP client fails at runtime. Price $0.05 USDC. POST /api/v1/soap-contracts/wsdl-xsd-dependency-audit. 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": {
      "wsdl": "<wsdl>",
      "schemas": "<schemas>"
    },
    "name": "soap-contracts_wsdl-xsd-dependency-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
wsdlYeswsdl, object. Required.
clientsNoclients, array. Optional.
schemasYesschemas, array. Required.
previousNoprevious, object. Optional.

Output Schema

NameRequiredDescriptionDefault
findingsNofindings. Array.
limitationsNolimitations. Array.
audit_statusNoaudit_status. String.
contract_changesNocontract_changes. Array.
dependency_graphNodependency_graph. Object.
affected_operationsNoaffected_operations. Array.
namespace_conflictsNonamespace_conflicts. Array.
unresolved_referencesNounresolved_references. Array.
breaking_change_candidatesNobreaking_change_candidates. Array.

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 cover read-only, idempotent, non-destructive and open-world behavior, and the description adds real context beyond them: imports are not fetched, a syntactic schema difference is not proof of runtime client failure, the price, the endpoint, and that an unpaid call returns x402 terms without running. It does not describe response shape, but an output schema exists to carry that.

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?

Purpose is front-loaded in the first sentence, followed by short, non-overlapping facts: status values, non-download of imports, the syntactic-vs-runtime caveat, then pricing and endpoint. Every sentence carries distinct information with no redundancy.

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?

Given a rich output schema, the description need not explain return values, and it helpfully enumerates the audit_status values up front. It remains slightly thin on the clients parameter and on any size/limit expectations, but nothing essential for making a correct call is missing.

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%, so the schema already documents all four parameters, which sets the baseline at 3. The description adds some meaning by characterizing "previous" as an optional prior document set to compare against, but says nothing about the clients array, which is the least self-explanatory parameter.

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?

States a specific verb and resources: "Compare a caller-supplied WSDL 1.1 document and its XSD documents, including an optional previous set." The scope (WSDL dependency audit) is clear enough to distinguish it from a generic schema tree tool, though it never names or contrasts the sibling soap-contracts_schema-dependency-tree.

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 implied by the phrasing: use it to compare a current document set against an optional "previous" set, and it discloses that imports are not downloaded so callers must supply all XSD documents themselves. However, there is no explicit when-to-use/when-not guidance and no comparison to the sibling alternative.

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