Skip to main content
Glama

Mitre Cwe

by io.github.pipeworx-io
OverviewDiscussionsAdmin

View

view
Read-onlyIdempotent

"Top 25 most dangerous software weaknesses" / "OWASP Top 10 CWE mapping" / "CWE view [N]" — fetch a curated CWE view (a published, opinionated selection of weaknesses). View 1003 = simplified mapping (NVD uses this), view 1387 = Top 25, view 1344 = OWASP Top 10. Returns the view's metadata plus the included CWE IDs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
ViewsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedOutput schema / properties / Views
      Added value: +{
+  "items": {
+    "properties": {
+      "ContentHistory": {
+        "items": {
+          "properties": {
+            "ModificationComment": {
+              "type": "string"
+            },
+            "ModificationDate": {
+              "type": "string"
+            },
+            "ModificationName": {
+              "type": "string"
+            },
+            "ModificationOrganization": {
+              "type": "string"
+            },
+            "ModificationReleaseDate": {
+              "type": "string"
+            },
+            "ModificationVersion": {
+              "type": "string"
+            },
+            "SubmissionDate": {
+              "type": "string"
+            },
+            "SubmissionName": {
+              "type": "string"
+            },
+            "SubmissionOrganization": {
+              "type": "string"
+            },
+            "SubmissionReleaseDate": {
+              "type": "string"
+            },
+            "SubmissionVersion": {
+              "type": "string"
+            },
+            "Type": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "ID": {
+        "type": "string"
+      },
+      "MappingNotes": {
+        "properties": {
+          "Comments": {
+            "type": "string"
+          },
+          "Rationale": {
+            "type": "string"
+          },
+          "Reasons": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "Usage": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "Members": {
+        "items": {
+          "properties": {
+            "CweID": {
+              "type": "string"
+            },
+            "ViewID": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "Name": {
+        "type": "string"
+      },
+      "Notes": {
+        "items": {
+          "properties": {
+            "Note": {
+              "type": "string"
+            },
+            "Type": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "Objective": {
+        "type": "string"
+      },
+      "References": {
+        "items": {
+          "properties": {
+            "ExternalReferenceID": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "Status": {
+        "type": "string"
+      },
+      "Type": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
    • removedOutput schema / properties / cwe_id
      Removed value: -{
-  "description": "View identifier",
-  "type": "string"
-}
    • removedOutput schema / properties / description
      Removed value: -{
-  "description": "View description",
-  "type": "string"
-}
    • removedOutput schema / properties / name
      Removed value: -{
-  "description": "View name",
-  "type": "string"
-}
    • removedOutput schema / properties / status
      Removed value: -{
-  "description": "Status of the view",
-  "type": "string"
-}
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "id": "1003"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "CWE view record from MITRE CWE API",
+  "properties": {
+    "cwe_id": {
+      "description": "View identifier",
+      "type": "string"
+    },
+    "description": {
+      "description": "View description",
+      "type": "string"
+    },
+    "name": {
+      "description": "View name",
+      "type": "string"
+    },
+    "status": {
+      "description": "Status of the view",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive, so the bar is lower. The description adds useful behavioral context beyond annotations: it explains that a view is a curated selection and states exactly what the response contains (view metadata plus included CWE IDs).

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?

The description is compact, front-loads the common aliases, and every clause adds value: purpose, concrete examples, and return contents. It is appropriately sized for a simple one-parameter tool and contains no filler or repetition.

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 output schema exists and annotations already cover safety, the description is nearly complete: it identifies the resource, the parameter's meaning, known key values, and the response shape. It does not explicitly explain when to use this instead of the weakness tool, but this is a minor gap rather than a missing requirement.

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 description coverage is 0%, so the description must compensate for the single 'id' parameter. It does so by providing concrete example IDs and explaining what they map to (1003 = NVD mapping, 1387 = Top 25, 1344 = OWASP Top 10). This gives the agent meaningful guidance even though it does not exhaustively describe all possible id formats.

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 fetches a curated CWE view, not an individual weakness, and uses specific verbs and resources. It also enumerates well-known view IDs (1003, 1387, 1344), which distinguishes the tool from sibling tools like weakness and category.

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 gives concrete when-to-use context by mapping view IDs to real-world use cases (NVD simplified mapping, Top 25, OWASP Top 10). It does not explicitly compare to alternative sibling tools, but the view-versus-weakness distinction is strongly implied and easy for an agent to act on.

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

All Mitre Cwe toolsInspect
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.

Resources