Skip to main content
Glama
SVerITG

Metis

by SVerITG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Metis · Data Guardian — Set Network Policy

set_network_policy

Set the network access policy for all agents to strict, normal, or offline to control internet access and block external requests.

Instructions

Set the current network access policy for all agents.

'strict'  — No internet access. Only local DB, files, and MCP tools.
'normal'  — Default. Librarian and News Radar may access allowed domains.
'offline' — Airplane mode. All external requests blocked.

Args:
    policy: One of 'strict' | 'normal' | 'offline'.

Input Schema

NameRequiredDescriptionDefault
policyYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It explains the effect of each policy mode (strict, normal, offline) and that it applies to all agents, but does not mention requirements, reversibility, or potential disruptions (e.g., dropping connections).

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 very concise, using a brief sentence followed by a bullet list and explicit args. No unnecessary words or redundancy.

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?

For a simple one-parameter setter with an output schema, the description covers the core functionality well. It could mention return behavior or confirmation, but the output schema likely covers that. Missing failure conditions or required permissions.

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 0%, so the description must compensate. It defines the only parameter 'policy' with three valid values and their meanings, which adds significant value beyond the empty schema. However, it could have listed the values as an explicit enum.

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 states it 'Set the current network access policy for all agents' and distinguishes three modes with explicit explanations. This differentiates it from the sibling 'get_network_policy' tool.

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?

The description explains what each policy does but does not provide when to use this tool versus alternatives. There is no mention of prerequisites, side effects, or guidance on when to choose which policy. However, the context is clear regarding the tool's function.

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