Skip to main content
Glama
Sign In
WET - Web Extended Toolkit

WET - Web Extended Toolkit

by n24q02m
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

config

Idempotent

Manage server settings, clear caches, reindex documentation, warm up services, and handle setup actions for the Web Extended Toolkit.

Instructions

Server config and management. Actions: status|set|cache_clear|docs_reindex|warmup|setup_sync|setup_status|setup_start|setup_skip|setup_reset|setup_complete. Use help tool with tool_name='config' for full docs.

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": {
      "action": "<action>"
    },
    "name": "config"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNo
forceNo
valueNo
actionYes
remote_typeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.7.3
  2. Removedv3.6.0
  3. Changed4 schema fields changedv3.5.0
    • addedOutput schema / additionalProperties
      Added value: +true
    • removedOutput schema / properties
      Removed value: -{
-  "result": {
-    "title": "Result",
-    "type": "string"
-  }
-}
    • removedOutput schema / required
      Removed value: -[
-  "result"
-]
    • changedOutput schema / title
      Previous value: -"configOutput"New value: +"configDictOutput"
  4. Changed2 schema fields changedv3.1.0
    • addedInput schema / properties / force
      Added value: +{
+  "default": false,
+  "title": "Force",
+  "type": "boolean"
+}
    • addedInput schema / properties / remote_type
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Remote Type"
+}
  5. First observedv2.13.0

TDQS

C2.6/5.0
Behavior2/5

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

The description does not disclose behavioral traits such as side effects, permissions, reversibility, or what happens on success/failure. The annotations indicate idempotent and non-destructive, but the description does not elaborate on these, leaving the actual behavior of actions like set or cache_clear unclear.

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?

The description is appropriately sized: it opens with a clear summary then lists actions in a compact, pipe-separated format. It is front-loaded with the main purpose and does not include unnecessary fluff.

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

Completeness2/5

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

Given the tool's apparent complexity (many distinct actions), the description is incomplete. It does not explain what each action does, any side effects, or required parameters for each action. It relies on the help tool for full docs, which is not sufficient for a complete understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds no meaning to the schema parameters. It lists actions but does not explain the role of 'key', 'force', 'value', or 'remote_type'. The schema provides types and defaults but no descriptions, so the parameter semantics are entirely undocumented.

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?

The description clearly states the tool's purpose as 'Server config and management' and enumerates specific actions (status, set, cache_clear, etc.), which gives a good high-level understanding. It is distinct enough from sibling tools, though it does not explicitly compare with them.

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?

The description does not explicitly state when to use this tool versus alternatives. It only suggests using the help tool for full documentation, which is a weak form of guidance. There is no indication of prerequisites or typical use cases for the listed actions.

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

Deploy Server

Other Tools