Skip to main content
Glama

set_project_network

Enable or disable outbound network access for a project's sandbox, allowing third-party code to reach the internet and local network when enabled.

Instructions

Enable or disable outbound network access for a project's sandbox. Enabling lets third-party code reach the internet and the local network.

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": {
      "project": "<project>",
      "enabled": "<enabled>"
    },
    "name": "set_project_network"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYes
projectYesInstalled project: its slug, or its id such as "github:owner/name".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses the security-relevant consequence of enabling (internet plus local network reach for third-party code), but says nothing about the default state, whether the change applies to an already-running sandbox or only future executions, whether it persists, or what is returned.

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, no waste, and the state-changing action is front-loaded ahead of the consequence. Each sentence contributes distinct information — one defines the operation, the other defines its effect.

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?

For a simple two-parameter toggle with no output schema the core is covered, but with zero annotation coverage the description should absorb more of the behavioral burden: default state, immediacy of effect, and permission requirements are all missing.

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 50%: 'project' is documented in the schema, while the boolean 'enabled' has no schema description. The description compensates by framing the operation as 'Enable or disable,' which makes the polarity of the boolean explicit where the schema is silent.

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 names a specific verb pair and resource: toggle outbound network access on a project sandbox. No sibling tool in the list performs an equivalent network-permission operation, so the purpose is unambiguous even without naming an alternative.

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?

Usage is implied by the disclosed consequence (third-party code reaching the internet and local network), which suggests when enabling is needed. There is no explicit when-to-use vs when-not framing, no mention of prerequisites such as a running sandbox, and no reference to any related sibling for the opposite operation.

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