Skip to main content
Glama

SubscriptionFlow

Book a SubscriptionFlow demo

sf_demo_booking
Read-only

Show a form to book a product demo. Collects name, email and company, then opens the scheduling page with those details pre-filled. The lead itself is captured by sf_request_demo. Public, read-only.

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": "sf_demo_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so 'Public, read-only' largely restates structured data. The genuinely additive part is the disclosed side effect: it collects three fields and opens an external scheduling page pre-filled, meaning the call drives user interaction rather than server data. It does not say what the call returns or how the interaction completes.

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?

Three short sentences, front-loaded with the core action and flow, with the sibling routing hint placed before the trailing safety note. The closing 'Public, read-only' is mildly redundant against the annotations but costs little.

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 zero-parameter, non-destructive UI tool with full annotation coverage and no output schema, the description covers what an agent needs: what appears, what is collected, what happens next, and which sibling handles the actual lead record. Nothing essential 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?

With zero parameters, the baseline is 4, and the description earns that by clarifying that name, email and company are gathered inside the rendered form rather than passed as tool arguments — a distinction the empty schema cannot convey on its own.

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?

The description uses a concrete verb+resource ('Show a form to book a product demo') and then spells out the flow — collect name/email/company, open the scheduling page pre-filled. It also draws a line against the sibling 'sf_request_demo' by stating the lead is captured there instead, so an agent can tell the two apart.

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

Usage Guidelines3/5

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

It implies usage context (a user wanting to book a demo) and usefully notes that actual lead capture belongs to `sf_request_demo`. However, it never states when to prefer this over the other form-style siblings like `sf_contact_form`, and no explicit prerequisite or exclusion is given.

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