Skip to main content
Glama

Server Details

Book London furniture assembly, wall mounting, handyman, electrical, and smart home jobs.

Status
Healthy
Last Tested
Transport
Streamable HTTP
URL

Glama MCP Gateway

Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.

MCP client
Glama
MCP server

Full call logging

Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.

Tool access control

Enable or disable individual tools per connector, so you decide what your agents can and cannot do.

Managed credentials

Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.

Usage analytics

See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.

100% free. Your data is private.
Tool DescriptionsB

Average 3.2/5 across 20 of 20 tools scored.

Server CoherenceA
Disambiguation4/5

Most tools have distinct purposes, but some overlap exists. For example, 'create_booking_request' and 'create_customer_booking' could be confused as both handle booking creation, though their descriptions clarify different stages. Similarly, 'start_customer_verification', 'verify_customer_otp', and 'verify_magic_link_token' all relate to verification but target specific methods. Overall, descriptions help differentiate, but a few tools have overlapping domains.

Naming Consistency5/5

Tool names follow a highly consistent verb_noun pattern throughout, such as 'check_availability', 'create_booking_request', and 'get_booking_status'. All names use snake_case uniformly, with clear verbs like 'check', 'create', 'get', 'list', 'start', 'verify', 'tag', and 'update'. There are no deviations in naming conventions, making the set predictable and readable.

Tool Count4/5

With 20 tools, the count is slightly high but reasonable for the domain of a booking and customer management system. It covers various aspects like availability checks, booking creation, payment handling, verification, and CRM operations. While it might feel heavy, each tool appears to serve a specific function in the workflow, so the count is appropriate with minor over-scoping.

Completeness5/5

The tool set provides comprehensive coverage for the booking and customer management domain. It includes CRUD-like operations (e.g., create, get, update, list), full lifecycle support from verification to payment and booking creation, and additional features like tagging and notes. There are no obvious gaps; agents can handle end-to-end workflows without dead ends.

Discussions

No comments yet. Be the first to start the discussion!

Try in Browser

Your Connectors

Sign in to create a connector for this server.

Resources