Skip to main content
Glama
Sign In
Code MCP Server

Code MCP Server

by agentics-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

add_allowed_command

Authorize a command for secure execution by adding it to the project's allowed commands list, enabling controlled use within the VS Code workspace.

Instructions

Add a command to the project's allowed commands list

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": "add_allowed_command"
  }
}

Input Schema

NameRequiredDescriptionDefault
commandYesCommand to add to allowed list

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3/5.0
Behavior1/5

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

No annotations provided, and description fails to disclose side effects (e.g., behavior if command already exists, validation, permissions, or reversibility). This is a mutable operation with zero 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.

Conciseness5/5

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

One short, clear sentence with no unnecessary information. Efficiently communicates the core purpose.

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 is simple with one parameter and no output schema, the description lacks completeness on idempotency, duplicate handling, and constraints, leaving an agent with unanswered questions.

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

Parameters3/5

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

Single parameter with 100% schema description coverage; the tool description adds no additional meaning beyond the schema's 'Command to add to allowed list'.

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?

Description clearly states the action 'add a command' and the resource 'project's allowed commands list', distinguishing it from sibling tools like 'remove_allowed_command' and 'get_allowed_commands'.

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 guidance on when to use this tool versus alternatives, no prerequisites mentioned, and no conditions like duplicates or error handling described.

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