Ietf Datatracker

Wgs Search

wgs_search

Read-onlyIdempotent

List all IETF working groups in Datatracker with pagination; returns acronyms, names, area, and charter status for every active and concluded WG.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`offset`	No

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 22, 2026

removedOutput schema / properties / count

Removed value: -{
-  "description": "Total number of working groups",
-  "type": "number"
-}

addedOutput schema / properties / meta

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

removedOutput schema / properties / next

Removed value: -{
-  "description": "URL to next page of results",
-  "type": [
-    "string",
-    "null"
-  ]
-}

addedOutput schema / properties / objects

Added value: +{
+  "items": {
+    "properties": {
+      "acronym": {
+        "type": "string"
+      },
+      "ad": {
+        "type": "null"
+      },
+      "charter": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "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",
+          "null"
+        ]
+      },
+      "resource_uri": {
+        "type": "string"
+      },
+      "state": {
+        "type": "string"
+      },
+      "time": {
+        "type": "string"
+      },
+      "type": {
+        "type": "string"
+      },
+      "unused_states": {
+        "items": {},
+        "type": "array"
+      },
+      "unused_tags": {
+        "items": {},
+        "type": "array"
+      },
+      "used_roles": {
+        "type": "string"
+      },
+      "uses_milestone_dates": {
+        "type": "boolean"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

removedOutput schema / properties / previous

Removed value: -{
-  "description": "URL to previous page of results",
-  "type": [
-    "string",
-    "null"
-  ]
-}

removedOutput schema / properties / results

Removed value: -{
-  "description": "Array of 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: +[
+  {
+    "limit": 100
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Paginated working groups list",
+  "properties": {
+    "count": {
+      "description": "Total number of working groups",
+      "type": "number"
+    },
+    "next": {
+      "description": "URL to next page of results",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "previous": {
+      "description": "URL to previous page of results",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "results": {
+      "description": "Array of 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

A4.2/5.0

Behavior4/5

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds valuable behavior details beyond that: it reveals the scope of results (active and concluded), the returned fields, and the use of pagination. It does not contradict the annotations.

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 a single, front-loaded sentence with no filler. It efficiently conveys the action, resource, scope, and return contents, making every word carry value. This is an example of concise and well-structured documentation.

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?

With an output schema present, the return structure is already defined, and annotations cover the safety profile. The description covers the main purpose and scope, and even lists return fields. The only notable missing piece is explicit parameter semantics, which is minor given the simplicity of the tool.

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 coverage for parameters is 0%, so the description must compensate. It mentions 'pagination' but does not explain the specific roles of limit and offset (e.g., limit = max results, offset = skip count). The example with limit:100 gives a weak hint, but the meaning is not explicit, leaving the agent to infer.

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 specifies a particular action ('List all IETF working groups in Datatracker'), the exact resource, and the scope ('every active and concluded WG'). It also enumerates the return fields (acronyms, names, area, charter status), which distinguishes it from the sibling tool 'wg' that presumably loads a single working group.

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 sets a clear context as a list-all operation with pagination, which implies it is for bulk retrieval rather than individual lookup (as in the sibling 'wg'). However, it does not explicitly name the alternative or state when not to use it, so the guidance is good but not fully explicit.

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.