Skip to main content
Glama
Sign In

The Guardian

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Sections

sections
Read-onlyIdempotent

List The Guardian's content sections (Politics, World, Sport, Culture, Environment, etc.). Optionally filter by name substring via q. Returns section IDs and titles for use as filters in search().

Input Schema

NameRequiredDescriptionDefault
qNo

Output Schema

NameRequiredDescriptionDefault
responseNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "q": "world"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "List of Guardian sections",
+  "properties": {
+    "response": {
+      "properties": {
+        "results": {
+          "description": "Array of section results",
+          "items": {
+            "properties": {
+              "apiUrl": {
+                "description": "Section API endpoint",
+                "type": "string"
+              },
+              "id": {
+                "description": "Section ID",
+                "type": "string"
+              },
+              "webTitle": {
+                "description": "Section web title",
+                "type": "string"
+              },
+              "webUrl": {
+                "description": "Section web URL",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "status": {
+          "description": "Response status",
+          "type": "string"
+        },
+        "userTier": {
+          "description": "User tier level",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false. The description confirms the tool is read-only and lists sections, adding minimal behavioral context beyond the annotations. 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.

Conciseness5/5

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

Two sentences, front-loaded with the main purpose and examples. No wasted words; every sentence adds value.

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?

The tool is simple with one optional parameter. An output schema exists, so detailed return value documentation is unnecessary. The description covers the essentials: listing sections, optional filtering, and the purpose of the output for use in search.

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%, but the description adds meaningful context for the 'q' parameter, explaining it filters by name substring. This compensates for the lack of schema documentation, though it does not provide full details like case sensitivity or exact matching.

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

Purpose4/5

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

Description states it lists The Guardian's content sections, provides examples, and mentions optional substring filtering. It also specifies that it returns section IDs and titles, indicating the purpose clearly. However, it does not explicitly distinguish from sibling tools like 'editions' or 'tags', so not a 5.

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

Usage Guidelines3/5

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

Description explains the optional filtering via 'q' and states the output is for use as filters in search(). This gives some usage context. However, it does not mention when not to use it or suggest alternatives like 'editions' for date-specific sections, which would improve guidance.

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

All The Guardian 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