Mitre Cwe

Descendants

descendants

Read-onlyIdempotent

"All weaknesses derived from [CWE]" / "full subtree below [N]" / "every variant of [X]" — full transitive descendants (children, grandchildren, …) of a CWE. Use for exhaustive coverage analysis — e.g. "every memory-safety weakness" via descendants of CWE-664/119.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description
`name`	No	Root CWE name
`cwe_id`	No	Root CWE identifier
`descendants`	No	Recursive array of descendant CWEs with their subtrees

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "id": "434"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Full descendant subtree of a CWE",
+  "properties": {
+    "cwe_id": {
+      "description": "Root CWE identifier",
+      "type": "string"
+    },
+    "descendants": {
+      "description": "Recursive array of descendant CWEs with their subtrees",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "name": {
+      "description": "Root CWE name",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedMay 18, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive. The description adds the behavioral trait of returning transitive descendants, which is beyond what annotations provide. No contradictions.

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 fairly concise with two sentences and an example. It is front-loaded with the key concept. Could be slightly more streamlined, but overall effective.

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 the annotations and presence of an output schema, the description provides adequate context for exhaustive coverage analysis. It explains the concept and usage, though it could elaborate on the format of returned data.

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 has one parameter 'id' with no description (0% coverage). The description does not explicitly define 'id' but implies it is a CWE identifier through examples. This is insufficient; it should directly state that 'id' is a CWE ID.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns 'full transitive descendants' of a CWE, using specific verbs like 'derived from' and examples. It distinguishes from sibling tools like 'children' by emphasizing exhaustive coverage.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states 'Use for exhaustive coverage analysis' and gives an example, implying when to use it. However, it does not explicitly mention when not to use it or name alternative tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Mitre Cwe tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.