Skip to main content
Glama
Sign In
Gravitas-Core-MCP

Gravitas-Core-MCP

by ahmed-coding
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

terminal_stop_background

Terminate a background process by specifying its process ID to stop the task and free up resources.

Instructions

Terminate a background process by process_id.

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": {
      "process_id": "<process_id>"
    },
    "name": "terminal_stop_background"
  }
}

Input Schema

NameRequiredDescriptionDefault
process_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It lacks details about side effects, error behavior, or whether termination is forceful or graceful. 'Terminate' implies destructiveness, but no safety info is given.

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 very brief (one sentence) and front-loaded with key info, but it lacks structure. While concise, it sacrifices necessary detail for the tool's complexity.

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

Completeness2/5

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

Given no output schema and a destructive action, the description is incomplete. It omits return values, error handling, and impact on other processes, leaving ambiguity for an AI agent.

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

Parameters1/5

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

Schema description coverage is 0%, and the description adds no meaning beyond the schema. The schema only defines process_id as a required string; the description does not clarify expected format, how to obtain the ID, or constraints.

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 the action (terminate), the target resource (background process), and the required identifier (process_id). It effectively distinguishes from sibling tools like terminal_start_background and terminal_list_background.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites, such as that the process must be currently running, or when not to use it (e.g., if the process is critical).

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