Skip to main content
Glama
Sign In
Keesan12

MartinLoop — Stop Runaway Loops, Bad Code & Token Waste

by Keesan12
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Local

Related Servers

Alternatives to MartinLoop — Stop Runaway Loops, Bad Code & Token Waste

Related Servers

  • Agent Cost MCP

    vk0dev
    A
    license
    Not graded
    quality
    B
    maintenance
    Local Cost Guard and runtime guardrails for AI agents in Claude Code.
    67 npm
    MIT

  • genpark-agent-budget-token

    alphaparkinc
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables autonomous agents to enforce financial guardrails by tracking real-time token burn and cost velocity, automatically throttling or freezing execution when budgets are exceeded. It also blocks destructive shell commands, prompt injections, and runaway planning loops while sanitizing outputs before they are returned.
    7
    MIT

  • genpark-agent-budget-token

    Alpha-Park
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables agents to track real-time token spend and cost velocity, automatically throttle or freeze execution when budgets are exceeded, and enforce sandbox and safety guardrails.
    7
    MIT
  • agentguard by agentwares

    agentguardofficial

    agentwares
    A
    license
    Not graded
    quality
    A
    maintenance
    Enforces policy controls for AI agents, including spend limits, action approvals, kill switch, scoped credentials, dry-run diffs, loop prevention, and auditable hash-chained logs.
    MIT
Deploy Server
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

TDQS

A3.7/5.0

Scored across 24 tools

Disambiguation3/5

The action tools (run, pause, cancel, continue, plan, preflight, estimate) are cleanly separable, but the read surface is crowded: martin_status, martin_get_run, martin_inspect, martin_run_dossier, martin_dossier, martin_logs, martin_get_verification_results and martin_eval all read the same persisted run records. The descriptions pre-empt confusion with explicit 'do not use X, use Y' cross-references, which helps, but that pattern itself signals overlapping purpose. martin_inspect vs martin_get_run vs martin_run_dossier remains a genuine three-way overlap an agent could easily misselect.

Naming Consistency4/5

All tools use the martin_ prefix with snake_case verb_noun structure (martin_get_run, martin_list_runs, martin_create_pr), which is highly predictable. A few names are noun-only or vague (martin_inspect, martin_status, martin_eval, martin_arcade), and descriptions reference a martin_get_status tool that is not in the set, slightly weakening the surface's internal consistency.

Tool Count3/5

At 24 tools this sits in the heavy band; the governed-run lifecycle genuinely is multi-stage, but at least four read/report variants (status, get_run, dossier, run_dossier) and two Arcade tools feel like they could be consolidated. Each tool has a stated purpose, so nothing is gratuitous, but the set is wider than an agent typically wants to navigate.

Completeness4/5

Coverage is strong across the lifecycle: diagnostics (doctor), estimation, planning, preflight, execution, hold/cancel/resume, listing and triage, run/attempt retrieval, verification evidence, grading, and PR summary/create/review. Minor gaps include no explicit retry/resume-run operation and dangling references to a martin_get_status tool that does not exist in this surface.

Maintenance

ActivityActive
ResponsivenessUnresponsive

Resources