Ietf Datatracker

Wg

wg

Read-onlyIdempotent

Working group by acronym.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`acronym`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`meta`	No
`objects`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 22, 2026

addedOutput schema / properties / meta

Added value: +{
+  "properties": {
+    "limit": {
+      "type": "number"
+    },
+    "next": {
+      "type": "null"
+    },
+    "offset": {
+      "type": "number"
+    },
+    "previous": {
+      "type": "null"
+    },
+    "total_count": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / objects

Added value: +{
+  "items": {
+    "properties": {
+      "acronym": {
+        "type": "string"
+      },
+      "ad": {
+        "type": "null"
+      },
+      "charter": {
+        "type": "string"
+      },
+      "comments": {
+        "type": "string"
+      },
+      "description": {
+        "type": "string"
+      },
+      "id": {
+        "type": "number"
+      },
+      "list_archive": {
+        "type": "string"
+      },
+      "list_email": {
+        "type": "string"
+      },
+      "list_subscribe": {
+        "type": "string"
+      },
+      "meeting_seen_as_area": {
+        "type": "boolean"
+      },
+      "name": {
+        "type": "string"
+      },
+      "parent": {
+        "type": "string"
+      },
+      "resource_uri": {
+        "type": "string"
+      },
+      "state": {
+        "type": "string"
+      },
+      "time": {
+        "type": "string"
+      },
+      "type": {
+        "type": "string"
+      },
+      "unused_states": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "unused_tags": {
+        "items": {
+          "type": [
+            null,
+            "string"
+          ]
+        },
+        "type": "array"
+      },
+      "used_roles": {
+        "type": "string"
+      },
+      "uses_milestone_dates": {
+        "type": "boolean"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

removedOutput schema / properties / results

Removed value: -{
-  "description": "Array of matching working groups",
-  "items": {
-    "properties": {
-      "acronym": {
-        "description": "Working group acronym",
-        "type": "string"
-      },
-      "description": {
-        "description": "Working group description",
-        "type": "string"
-      },
-      "name": {
-        "description": "Working group name",
-        "type": "string"
-      },
-      "state": {
-        "description": "Working group state",
-        "type": "string"
-      },
-      "type": {
-        "description": "Working group type",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "type": "array"
-}

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "acronym": "quic"
+  },
+  {
+    "acronym": "httpbis"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Working group response from IETF Datatracker API",
+  "properties": {
+    "results": {
+      "description": "Array of matching working groups",
+      "items": {
+        "properties": {
+          "acronym": {
+            "description": "Working group acronym",
+            "type": "string"
+          },
+          "description": {
+            "description": "Working group description",
+            "type": "string"
+          },
+          "name": {
+            "description": "Working group name",
+            "type": "string"
+          },
+          "state": {
+            "description": "Working group state",
+            "type": "string"
+          },
+          "type": {
+            "description": "Working group type",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedMay 14, 2026

TDQS

C2.2/5.0

Behavior2/5

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

Annotations already carry the safety profile (readOnly, openWorld, idempotent, non-destructive), so the bar is lowered. However, the description adds nothing beyond a bare resource label — it does not specify what data is returned, how the acronym should be formatted (case, hyphenation), or any limits. With openWorldHint set, there is no disclosure that results may be partial or time-bounded.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Six words with no waste, and the key term is front-loaded. But this is under-specification rather than genuine conciseness; the brevity comes at the cost of omitting purpose, usage, and parameter detail.

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

Completeness3/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-value documentation is not the description's burden. Yet for a tool with zero schema description coverage, lacking any usage note or input-format guidance leaves the definition incomplete for confident invocation.

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 description coverage is 0%, so the description must compensate for the single parameter. It only echoes the parameter name ('by acronym') without specifying expected format, case sensitivity, or whether it is an exact or fuzzy match — leaving the agent to guess about the input contract.

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

Purpose2/5

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

The description identifies the resource type ('working group') and lookup key ('acronym'), but it is a noun phrase with no verb — it never states what the tool does (fetch, return, resolve?). With siblings like wgs_search and rfc present, there is no articulation of how this differs, making the purpose only weakly inferable.

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

Usage Guidelines2/5

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

No when-to-use guidance, no exclusions, and no mention of alternatives such as wgs_search despite being a plausible sibling for the same resource. The description gives no context for choosing this tool over its neighbors.

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

All Ietf Datatracker 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.

Wg

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources