Skip to main content
Glama
Claude Free Code MCP

Claude Free Code MCP

by ImIpscanning

run_task

Destructive

Execute predefined npm or git tasks such as test, build, lint, format, typecheck, git-status, or git-diff, with human approval required for build, test, lint, format, and typecheck.

Instructions

Execute a predefined npm or git task; build/test/lint/format/typecheck require local human approval.

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": {
      "task": "<task>"
    },
    "name": "run_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesTask name
timeoutSecondsNoMaximum duration in seconds 1..180

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Adds genuinely useful behavior beyond the annotations: four of the seven tasks (build/test/lint/format/typecheck) require local human approval, so the agent knows to expect a gate. The annotations already cover the mutation profile (destructiveHint=true, openWorldHint=false), and the description does not say what happens if approval is denied or how git-status/git-diff differ in risk, keeping it out of 5 territory.

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?

A single front-loaded sentence with the action first and the approval constraint second; no filler, and both clauses carry information the agent needs.

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 two-parameter tool with a fully documented schema, the description covers purpose and the main operational caveat (approval gating). It stops short of describing output or whether a pending approval blocks the call, which would matter for a tool with no output schema.

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 description coverage is 100%: the task enum is fully enumerated and timeoutSeconds is documented with its default and 1..180 range. The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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 (execute) and resource (predefined npm or git task), and the enum in the schema pins the exact task set. It implicitly distinguishes itself from the arbitrary-command sibling run_command by saying 'predefined', but never names that alternative, so the differentiation requires inference.

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 word 'predefined' implies this is for the fixed task set rather than arbitrary commands, and the approval clause signals the friction involved. However, there is no explicit when-to-use/when-not guidance and no mention of run_command as the escape hatch for commands outside the enum.

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