Skip to main content
Glama
Sign In
devpulse-mcp

devpulse-mcp

by loxhness
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_running_services

Checks common development ports to list running processes and identify expected services that are missing.

Instructions

Lists processes running on common dev ports (3000, 4000, 5173, 8080 etc). Shows what is running and what is expected but missing.

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

Input Schema

NameRequiredDescriptionDefault
cwdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool shows running and missing processes on specific ports, but does not mention side effects, permissions, or any limitations beyond the listed ports.

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 clear sentences with no redundant information. Each sentence adds value: first states what it does, second adds the expected-but-missing aspect.

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 the lack of output schema and minimal parameter documentation, the description omits important details such as return format, what 'expected but missing' means, and how the cwd parameter affects the output. More context would be beneficial for a complete understanding.

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?

The input schema has one parameter (cwd) with no description, and schema description coverage is 0%. The description does not explain what cwd does or how it affects the results, leaving the agent with no guidance on its usage.

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 ('lists') and resource ('processes on common dev ports'), and distinguishes the tool from siblings by focusing on a specific set of ports and including expected but missing processes.

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 description implies the tool is for checking processes on common dev ports, but does not explicitly state when to use it versus alternatives like get_recent_errors or get_session_snapshot, nor does it provide any exclusions or prerequisites.

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