Skip to main content
Glama

SubscriptionFlow

Request a SubscriptionFlow demo

sf_request_demo
Read-only

Submit a request for a SubscriptionFlow demo. Validates and stores/forwards the request and returns a generic acknowledgement. Public, read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "email": "<email>"
    },
    "name": "sf_request_demo"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoYour name. Optional.
emailYesA work email address.
companyNoYour company. Optional.
messageNoAnything you want the team to know. Optional.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds real context — validation occurs, the payload is stored/forwarded, and the response is a generic acknowledgement. However, 'stores/forwards' sits in mild tension with readOnlyHint and is left unexplained, and nothing is said about rate limits, spam handling, or failure behavior on invalid input.

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?

Two tight sentences, front-loaded with the action and followed by outcome information. No filler wording and nothing repeated from the title or annotations.

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?

For a simple four-field public form submission with a fully documented schema and no output schema, the description covers the essentials, including what comes back ('a generic acknowledgement'). It falls short only on edge-case behavior, such as what happens when validation fails or whether duplicate submissions are deduplicated.

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?

Schema description coverage is 100%, so every parameter already carries its own description including the 'work email address' note for the required email field. The description adds no further meaning about parameter formats or constraints, which is acceptable given the schema does the work.

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 gives a specific verb and resource: 'Submit a request for a SubscriptionFlow demo.' Combined with the title, an agent can distinguish it from sibling lead-capture tools such as sf_contact_form or sf_contact, though the description itself never names or contrasts with those siblings.

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?

Usage is only implied. The phrase 'Public, read-only' signals this is a safe, unauthenticated call, but there is no explicit statement of when to choose this tool over sf_demo_booking or sf_contact_form, nor any preconditions such as requiring a work email domain.

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