Skip to main content
Glama

Marco Collin Stolk – AI-begeleiding

get_service_catalog

Read-onlyIdempotent

Read Marco Collin Stolk’s public AI coaching services in Limburg, introductory-session price and contact route. No booking, messaging or payment. No account or API key required.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
nameYes
sameAsYesOfficial profiles identifying Marco Collin Stolk.
bookingYes
contactYes
servicesYes
paginationYesThe whole catalog is returned in one response; no next page.
descriptionYes
start_sessionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 the safety profile is covered; the description still adds genuinely new facts: no account or API key is needed and no side effects occur. That auth-and-side-effect disclosure is exactly the value-add expected beyond annotations, though it says nothing about data freshness or rate limits.

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?

Three short sentences, front-loaded with what is returned and immediately followed by the negative scope and auth requirements. No filler, no repetition of the tool name, every clause carries 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 an output schema present, return shape needs no explanation, and the description covers the remaining gaps an agent would care about: data source, locality, auth, and absence of side effects. Only minor operational details (freshness, whether the catalog can be empty) are unaddressed.

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 and the schema is an empty object with additionalProperties false, so there is no parameter meaning to explain — the baseline for a 0-param tool applies. The description correctly implies the call is argument-free.

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?

"Read ... public AI coaching services in Limburg" gives a concrete verb and resource and enumerates the payload (services, introductory-session price, contact route), so an agent knows exactly what comes back. No sibling tools exist, so there is nothing to differentiate against, which is the only thing keeping this from a 5.

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 description draws hard scope boundaries — "No booking, messaging or payment" — which tells the agent when this tool is not the right call and prevents it from being mistaken for a transactional endpoint. It does not state a positive trigger phrase (e.g., "use when the user asks about services or pricing"), so it stops short of explicit when-to-use guidance.

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.