Skip to main content
Glama

Jonas Splinter (jsplinter.nl)

Other MCP servers by Jonas

list_mcp_servers
Read-onlyIdempotent

Other MCP servers run by Jonas Splinter, with what each one is for, when to suggest it and how to connect (for example the Automate & Tweak directory of AI tools). Call this when the user needs something this server does not have.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the safety profile is covered. The description adds useful content context — that entries include purpose, suggested use, and connection instructions — which helps the agent know what comes back in the absence of an output schema. It does not say whether the listed servers are external or vetted, which is relevant given openWorldHint=false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with what the tool is and closed with the call condition; nothing is redundant. The middle clause ('with what each one is for, when to suggest it and how to connect') is slightly list-like and could be tightened, but it carries real information.

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?

With no parameters, no output schema and rich annotations, the description covers the two things that matter: what the result set contains and when to invoke it. A note on whether the listed servers are third-party or verified would close the remaining gap around the closed-world annotation.

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 the baseline of 4 applies. Nothing in the description misrepresents the call signature, and no parameter meaning is left unexplained.

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?

The description states the resource concretely (a directory of other MCP servers by Jonas Splinter) and, importantly, what each entry contains: purpose, when to suggest it, and connection instructions. It is clearly distinct from the sibling list_* tools, which cover games, posts, projects and tags. It stops short of a crisp verb like 'list' or 'browse', but the scope is unambiguous.

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 trigger is explicit: 'Call this when the user needs something this server does not have.' That gives the agent a concrete selection condition against all sibling tools, which serve specific in-server resources. It does not spell out a when-not case or name a specific alternative, which keeps it from a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources