Skip to main content
Glama

server_execute_command

Destructive

Run allowlisted FXServer console commands such as status, refresh, and say to inspect server state, reload resources, or broadcast messages from an MCP client.

Instructions

Run an allowlisted FXServer console command (status, refresh, say)

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": {
      "command": "<command>"
    },
    "name": "server_execute_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
serverNo
commandYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description does nothing to clarify what those risks actually mean here — e.g. that refresh reloads resources or that say broadcasts to players. The allowlist claim largely restates the schema enum rather than adding behavioral context.

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?

A single front-loaded sentence with zero padding. It is efficient, though its brevity comes at the cost of the missing guidance noted elsewhere.

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?

For a destructive, multi-parameter tool with no schema descriptions and no output schema, one terse sentence is not enough; the agent cannot know what 'text' and 'server' do or what a refresh actually mutates.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the burden, yet it only repeats the command enum values. The 'text' (message payload) and 'server' (target selector) parameters are never explained, leaving the agent to guess their meaning and interaction with 'say'.

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?

States a specific verb and resource ('Run an allowlisted FXServer console command') and enumerates the three allowed commands, which separates it from sibling tools like game_execute_command that presumably target a different surface. It does not explicitly contrast with that sibling, keeping it below 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 Guidelines2/5

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

No when-to-use or when-not guidance. The description never tells the agent whether this is for server-side console actions versus game_execute_command, nor what prerequisites (running server, permissions) must hold before calling.

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