Skip to main content
Glama
Sign In
@arcwall/mcp-server

@arcwall/mcp-server

by rom-baro
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

arcwall_pre_commit

Scan staged files for secrets and validate MCP configurations before commit to prevent security issues.

Instructions

Security check before committing. Scans staged files for secrets and checks MCP configs. Returns CLEAR TO COMMIT or BLOCKED with issues to fix.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "arcwall_pre_commit"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoRepository directory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states what is scanned and returned, but does not disclose whether the tool modifies any files, required permissions, or potential side effects.

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 fluff, clearly structured with input, action, and output. Every sentence adds value.

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?

Given the simplicity of the tool, the description covers purpose, action, and return value. Lacks error handling or prerequisites, but sufficient for a pre-commit check.

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?

Schema coverage is 100% and the parameter 'path' is described. The description adds context about 'staged files' but does not significantly elaborate beyond the schema.

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 is a security check before committing, scans staged files for secrets and MCP configs, and returns a status. This distinguishes it from sibling tools that focus on individual scans.

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 implies use before committing ('Security check before committing'), but does not explicitly state when to use this versus the sibling tools, nor does it provide exclusions or alternatives.

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