mitre-cwe-mcp-server

Get CWE view

cwe_get_view

Read-onlyIdempotent

Read a CWE view objective, audience, status, source filter, recorded notes, and direct members in published order. Navigation views list top-level members rather than every descendant; use cwe_get_hierarchy for navigation or cwe_search_weaknesses with viewId for weakness membership closure. A filter-defined (Implicit) view lists no members: its filterDefinition is the source XPath that defines membership, and cwe_search_weaknesses with its viewId returns the weaknesses that filter selects; when the filter has a part this server does not evaluate, the guidance says so and that search returns none with a disclosure. Unknown and non-view IDs return a structured miss. Follow nextCursor for remaining direct members.

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": {
      "id": "<id>"
    },
    "name": "cwe_get_view"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	CWE view ID such as CWE-1000 or 1000; discover with cwe_list_reference topic views.
`limit`	No	Maximum page size; capped at 100 items with disclosure.
`cursor`	No	Opaque continuation returned by this tool.

Output Schema

Name	Required	Description
`id`	No	Canonical requested CWE ID.
`cap`	No	Effective page limit.
`name`	No	Source view name.
`type`	No	Source view type.
`error`	No	Present when the call failed. Absent on success.
`found`	No	Whether this ID resolves to a CWE view.
`notes`	No	Notes MITRE records for this entry, in source order; absent when none are recorded.
`shown`	No	Page item count.
`notice`	No	Page cap disclosure.
`reason`	No	Missing record or known non-view.
`status`	No	Source status.
`members`	No	Direct members in source order.
`audience`	No	Source audience.
`guidance`	No	View discovery or empty-members guidance.
`objective`	No	Complete source objective in CommonMark.
`sourceUrl`	No	Official view definition URL.
`truncated`	No	Whether more direct members remain.
`pagination`	No	Local result pagination.
`provenance`	No	Loaded catalog provenance.
`totalCount`	No	Direct members before paging.
`appliedFilters`	No	Applied inputs and defaults.
`filterDefinition`	No	Source XPath filter defining a filter-defined view’s membership, exactly as published.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 11, 2026

changedInput schema / properties / limit / description

Previous value: -"Maximum page size; capped at 100 and a 24,000-byte response budget with disclosure."New value: +"Maximum page size; capped at 100 items with disclosure."

Changed4 schema fields changedNov 2, 2026

addedOutput schema / properties / members / items / properties / dimensions

Added value: +{
+  "description": "Recorded dimensions in source order.",
+  "items": {
+    "additionalProperties": false,
+    "description": "Recorded typed dimension.",
+    "properties": {
+      "type": {
+        "description": "Source dimension type.",
+        "type": "string"
+      },
+      "value": {
+        "description": "Source dimension value.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "value"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / properties / members / items / properties / type / enum

Previous value: -[
-  "weakness",
-  "category",
-  "view"
-]New value: +[
+  "weakness",
+  "category",
+  "grouping",
+  "view"
+]

addedOutput schema / properties / notes / items / properties / releaseDate

Added value: +{
+  "description": "Source note release date.",
+  "type": "string"
+}

addedOutput schema / properties / notes / items / properties / version

Added value: +{
+  "description": "Source note version.",
+  "type": "string"
+}

First observedOct 23, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld, and the description adds substantial behavior beyond that: navigation views return only top-level members, implicit views return no members and expose an XPath filterDefinition, unsupported filter parts are disclosed and search returns none, and unknown/non-view IDs yield a structured miss. Pagination behavior via nextCursor is also disclosed.

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?

Front-loaded with what is read, then alternative routing, then the implicit-view exception, then pagination. Dense but nearly every sentence carries a distinct fact; the implicit-view sentence is long and slightly convoluted but not redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter read tool with an output schema, this covers the remaining gaps an agent needs: member scope per view type, empty-result explanations, failure signaling for bad IDs, and pagination. Nothing material is left to inference.

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%, so id format, limit cap, and cursor opacity are already documented. The description still adds meaning by explaining that nextCursor pages through remaining direct members, tying cursor semantics to the direct-member model rather than generic paging.

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?

States a specific verb ('Read') plus the exact resource and enumerates what is returned: objective, audience, status, source filter, notes, and direct members in published order. It also distinguishes itself from siblings by naming cwe_get_hierarchy and cwe_search_weaknesses as the tools for other access patterns.

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

Usage Guidelines5/5

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

Explicit routing guidance: use cwe_get_hierarchy for navigation and cwe_search_weaknesses with viewId for weakness membership closure. It further explains the special case of filter-defined (Implicit) views and that their membership must be obtained via search rather than this tool.

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

All mitre-cwe-mcp-server 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.