Skip to main content
Glama

Jonas Splinter (jsplinter.nl)

List projects

list_projects
Read-onlyIdempotent

The businesses and side projects of Jonas Splinter (Blockspot.io, VoucherAlarm, Automate & Tweak, JSplinter Games) with a one-line description, his role, the project website and its page on jsplinter.nl. Call get_project with a key for the details.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety needs no repetition. The description adds genuinely new behavior context: the shape of each row (description, role, website, page link) and the existence of a keyed follow-up call, which substitutes for the missing output schema.

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 the resource and followed by the routing hint. The parenthetical roster of project names is slightly bulky but does signal to the agent what content to expect from an empty-parameter call.

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 list tool with no output schema, the description covers purpose, row contents, and the next-step call, which is nearly everything an agent needs. Only minor gaps remain, such as whether the list is exhaustive or ordered.

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 and the schema is fully self-describing. The only mention of a 'key' is correctly attached to the sibling get_project rather than to this call, which avoids confusion.

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 (list) and resource (projects) and immediately enumerates the fields each entry contains (one-line description, role, website, jsplinter.nl page). It also names the sibling get_project that returns details, so the agent can separate the two without opening a schema.

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?

Explicitly routes detail lookups to get_project with a key, which gives a clear this-vs-alternative rule. It does not address when a caller should prefer this list over other list_* tools, but the resource distinction is self-evident from the names.

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