yesmcp

Show yesmcp's services

services_widget

Read-onlyIdempotent

Shows yesmcp's services as an interactive card carousel right in the chat: what we build, hosting & monitoring, security, ownership. Each card lets the user book a scoping call without leaving the widget (through book_consult — every booking rule applies). Prefer this over get_services when the user asks what yesmcp does or offers and this client can render interactive tools. Read-only: browsing stores nothing.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`services`	Yes	yesmcp's service catalog, carousel order.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 6, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already carry readOnly/idempotent/non-destructive safety. The description adds genuine context beyond them: the interactive carousel behavior, the in-widget booking flow routed through book_consult with 'every booking rule applies,' and the concrete claim that 'browsing stores nothing.' No contradiction with annotations.

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 sentences with no waste: core function, booking interaction, then routing and read-only note. Every sentence earns its place and key facts are front-loaded.

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

Completeness5/5

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

For a 0-parameter widget with an output schema and safety annotations, the description covers what it shows, when to select it over get_services, how its booking interaction behaves, and its storage footprint. Nothing needed for correct invocation is missing.

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 has zero parameters and schema coverage is trivially 100%, so there is nothing for the description to explain about inputs. This meets the baseline-4 expectation for a parameterless tool.

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 and resource — 'Shows yesmcp's services' — and adds the rendering format (interactive card carousel) with the content areas covered. Explicitly contrasts with get_services, so an agent can distinguish it from siblings without opening schemas.

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

Usage Guidelines5/5

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

Gives an explicit routing rule: 'Prefer this over get_services when the user asks what yesmcp does or offers and this client can render interactive tools.' It names the alternative, states the condition, and implies the inverse (use get_services when interactive rendering is unavailable).

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

All yesmcp tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0

Disambiguation4/5

Most tools are clearly distinct: booking lifecycle (book, cancel, reschedule, availability), services, scenarios, and meta tools each target different actions. The widget/non-widget pairs (book_consult vs booking_widget, get_services vs services_widget) and list_availability vs booking_widget could cause confusion, but the descriptions explicitly state which to prefer and when.

Naming Consistency3/5

Most tools follow verb_noun (book_consult, cancel_booking, reschedule_booking, get_services, list_availability, advise_scenarios), but four break the pattern with noun_noun or gerund forms (booking_widget, services_widget, directory_census, demo_walkthrough). The mix is readable but inconsistent, especially the widget pairings that differ from their non-widget counterparts.

Tool Count5/5

Ten tools is well-scoped for a consultation and advisory service server. Each tool earns its place: full booking lifecycle, services catalog, scenario playbooks, and reviewer-facing meta tools. No redundant or filler tools.

Completeness4/5

The booking lifecycle is fully covered (list, book, cancel, reschedule) plus interactive widgets, and services/scenario discovery is solid. The only notable gap is that cancel/reschedule require the email confirmation reference — there is no 'list my bookings' tool to look up bookings by email. The demo/census tools are meta but deliberately scoped.

Resources

Need Help?