Skip to main content
Glama
mcp-feature-test

mcp-feature-test

by linuxrrze

List clients seen by this server

list_seen_clients
Read-only

List every distinct client that has connected to this server process since startup, including name, version, protocol version, transport, and capabilities, most recent first. Useful when testing several frontends against one HTTP server.

Instructions

List every distinct client (name, version, protocol version, transport, capabilities) that has talked to this server process since it started, most recent first. Useful when testing several frontends against one HTTP server.

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_seen_clients"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.9/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile, so the description's job is to add context — and it does: the data is per-process and resets when the server restarts ("since it started"), results are ordered most recent first, and entries are deduplicated by distinct client. That is exactly the kind of state/lifetime disclosure an agent needs. It does not discuss volume or limits, so not a 5.

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, zero filler. The scope and ordering are front-loaded, and the returned-fields parenthetical is compact rather than a bulleted dump.

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-parameter read tool with no output schema, the description carries the necessary load by naming the returned fields, the ordering, and the data lifetime. Minor gap: no sense of expected result size or whether the list persists across restarts beyond the implied per-process scope.

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 takes zero parameters, so there is nothing for the description to disambiguate beyond the empty schema; baseline 4 applies. The description correctly implies a no-argument call with no filtering options.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("List every distinct client") and pins the scope precisely: clients that have talked to this server process since it started, most recent first. It even enumerates the returned fields (name, version, protocol version, transport, capabilities). It stops short of naming the sibling inspect_client as the single-client alternative, so it does not fully differentiate by name.

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?

Provides an implied usage context ("Useful when testing several frontends against one HTTP server"), which tells the agent this is a diagnostic/inventory tool. However, it gives no explicit when-not guidance and does not point to inspect_client for drilling into a single client, leaving the agent to infer the split.

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