Skip to main content
Glama
Sign In
mcp-bridge

mcp-bridge

by ctrlpi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

mcp_script_list

Lists files in a specified agent's scripts folder and reports write permissions (enabled, default key, or locked) to verify if writes are allowed.

Instructions

List the files in agent's scripts/ folder (the folder sensors run from): scripts ([{name, size, modified}]) and write: "enabled", "default_key" (writes are refused until the agent's api_key is changed from the default) or "locked" (a write.lock file there blocks every write).

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": {
      "agent": "<agent>"
    },
    "name": "mcp_script_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.9.30

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the return shape and explains important write states, including that writes are refused until the API key is changed and that a write.lock blocks every write. It does not explicitly state read-only/auth prerequisites for listing, but the operation is self-evidently non-mutating.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is short and front-loads the purpose, but it is a dense run-on sentence with embedded return-shape syntax and three write-status definitions. It is concise in length but less clear structurally than it could be.

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 one-parameter list tool with no output schema, the description supplies the essential return details and write-state semantics. It omits the `agent` value format and error behavior, but covers most of what an agent needs to call the tool correctly.

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 coverage is 0%, so the description should compensate. It only implicitly identifies `agent` as the owner of the scripts folder and never says whether the value is a name, ID, or slug, leaving the sole parameter underspecified.

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 states a specific verb ('List'), a specific resource ('files in `agent`'s scripts/ folder'), and scope ('the folder sensors run from'). The return detail and write-status explanation further pin down what the tool does, and the list framing distinguishes it from sibling read/write/run operations.

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 operational context: listing scripts and checking write status before reading, running, or writing. However, the description never explicitly says when to use this versus mcp_script_read, mcp_script_write, or mcp_script_run, so the agent must infer the workflow.

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