Skip to main content
Glama

Little Works

list_booking_services

Services on a schedule (prices, duration, linked materials).

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

Input Schema

NameRequiredDescriptionDefault
scheduleSlugNoDefault little-works-construction

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden, yet it says nothing about read-only nature, pagination, authorization, or ordering. The only behavioral content is the hint at returned fields (prices, duration, linked materials), which is thin for a tool with zero annotation coverage.

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

Conciseness3/5

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

It is short and front-loaded with no waste, but it is a telegraphic fragment lacking a verb, which makes it feel under-specified rather than efficiently concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description is the only source of information about what this tool returns, and it supplies only a bare parenthetical field list. The optional scheduleSlug scoping and the shape of results are left undocumented, which is insufficient for a list tool with a parameterized scope.

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?

There is a single optional parameter (scheduleSlug) whose schema description is present, giving 100% coverage, so the baseline is 3. The description adds no meaning about what a schedule slug is or what the default 'little-works-construction' implies for results.

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

Purpose3/5

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

The description is a noun fragment ('Services on a schedule') rather than a verb+resource statement, though the tool name and the parenthetical field list do make it clear this returns bookable services tied to a schedule. It gives no differentiation from siblings such as list_materials or list_appointments, so an agent must guess how this differs from other list tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. The agent is left to infer that this is a read/list operation from the name prefix alone.

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