Skip to main content
Glama

Score schema dependency weight

soap-contracts_schema-dependency-tree
Read-onlyIdempotent

Read import, include, and complexType names from the supplied XML. A document cycle, or a complex type that references itself, sets the circular flag. The score counts types, imports, and non-builtin references. schemaLocation values are not downloaded. Price $0.04 USDC. POST /api/v1/soap-contracts/schema-dependency-tree. 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": {
      "documents": "<documents>"
    },
    "name": "soap-contracts_schema-dependency-tree"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentsYesdocuments, array. Required.

Output Schema

NameRequiredDescriptionDefault
dependency_tree_jsonNodependency_tree_json. Array.
schema_complexity_scoreNoschema_complexity_score. Number.
circular_dependency_detectedNocircular_dependency_detected. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld behavior, so the description is not carrying the safety burden. It still adds real context beyond them: no remote fetching of schemaLocation, the $0.04 USDC price, the POST endpoint, and the fact that an unpaid call returns x402 payment terms without executing — the last being genuinely important pre-call knowledge.

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?

Behavior is front-loaded in the first three sentences, followed by scope, price, and endpoint details. Every sentence carries information, though the raw endpoint path is lower value for an agent than the cycle/score semantics.

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?

An output schema exists, so return values need not be explained, yet the description still clarifies what the circular flag means and how the score is composed. Payment and non-fetching behavior round out what an agent needs; only sibling differentiation 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 description coverage is 100% and there is only one required parameter (documents), so the schema already explains name and content constraints. The description adds only that the content is XML to be parsed for imports/includes/complexTypes, which is marginal but not zero 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?

States a specific verb and resource: reads import/include/complexType names from supplied XML, detects cycles (circular flag), and computes a score from types, imports, and non-builtin references. That is concrete enough to act on, but it never differentiates itself from the sibling soap-contracts_wsdl-xsd-dependency-audit, so an agent must guess which analyzer to pick.

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 rather than prescribed: the agent can infer you call this when you have XML documents and want dependency weight. There is no explicit when-to-use/when-not guidance and no routing to the sibling audit tool, though the note that schemaLocation values are not downloaded does set a scope boundary.

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