Skip to main content
Glama

List MCP servers

list_mcp_servers
Read-onlyIdempotent

List MCP servers registered in local harness configs, showing which executables exist on this machine and which are configured only, with an option to report installed servers alone.

Instructions

List MCP servers registered in the harness configs on this machine, distinguishing those whose executable is present from those that are configured only. Not covered by list_sources, which lists corpora of skills and agents.

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

Input Schema

NameRequiredDescriptionDefault
installed_onlyNoReport only servers whose command resolves on this machine.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds real context beyond that: results come from local harness config files and distinguish runnable servers from merely configured ones, which tells the agent what the output means. It stops short of noting whether config paths or parse failures are reported.

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?

Two sentences, both load-bearing: the first defines scope and output distinction, the second handles sibling disambiguation. The scoping information is front-loaded with no filler or restatement of the title.

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 zero-required-parameter read tool with full annotation coverage and no output schema, the description supplies nearly everything an agent needs: source of truth, filtering distinction, and sibling boundary. Only minor items, such as whether it reports config locations or handles missing/corrupt configs, are left unstated.

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 coverage is 100% and the single optional parameter installed_only is documented in the schema as 'report only servers whose command resolves on this machine.' The description describes that same installed-vs-configured distinction but never ties it to the parameter, so it adds no syntax or usage detail beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource (list MCP servers) plus the precise data source (harness configs on this machine) and the key distinction it surfaces (executable present vs. configured only). It also explicitly disclaims coverage of list_sources, so an agent can separate it from that sibling without inspecting schemas.

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?

Names the nearest alternative (list_sources) and states the boundary: that tool lists corpora of skills and agents, not MCP servers. Usage is therefore clearly implied for 'what MCP servers are configured here' questions, but there is no explicit when-not-to-use guidance or mention of other siblings such as proxy_discover.

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