Skip to main content
Glama
Sign In
Code Expert MCP Server

Code Expert MCP Server

by lfnovo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

stop_auto_refresh

Stop automatic repository refreshing to prevent unwanted updates. Cancels scheduled refreshes and halts background worker until system restart.

Instructions

Manually stop the auto-refresh system.

    This will cancel all scheduled refreshes and stop the background worker.
    Repositories will no longer be automatically refreshed until the system is restarted.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description fully discloses behavioral consequences: cancels scheduled refreshes, stops the background worker, and remains inactive until restart. This provides clear side-effect awareness beyond the tool name.

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?

The description is two sentences, front-loaded with the key action, and every sentence adds essential context (scope and consequences). No filler or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, no-output tool, the description covers purpose, side effects, and persistence until restart. It is fully sufficient for an agent to select and invoke this tool correctly.

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

Parameters4/5

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

The tool has zero parameters, and the input schema is empty, so there is nothing to explain. The baseline of 4 applies as the description need not add parameter details.

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 uses a specific verb 'stop' with resource 'auto-refresh system', clearly stating the tool's function. It naturally distinguishes from sibling tools like start_auto_refresh and get_auto_refresh_status by naming the action it performs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context by stating 'Manually stop' and explaining the effect on repositories ('no longer automatically refreshed'). It does not explicitly name alternatives or exclusions, but the action is unique among siblings, so the usage is clear enough.

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