Skip to main content
Glama

SubscriptionFlow

About SubscriptionFlow

sf_product_info
Read-only

Show what SubscriptionFlow does — features, the industries it serves, integrations, benefits or how pricing works. Use topic "all" to show everything at once. 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_product_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNoWhich area to show. Defaults to all.

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, destructiveHint=false, and openWorldHint=false, and the description mostly echoes this with 'Public, read-only.' The word 'Public' adds a small amount of new information (no authentication or account context required), but nothing is said about response shape, size, or any limits. With annotation coverage present, this is adequate but not additive.

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?

Two short sentences, front-loaded with the core purpose followed by the parameter shortcut. The comma list partially duplicates the enum in the schema, which is mild redundancy, but nothing is padded or buried.

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?

A single optional enum parameter, no output schema, and fully specified annotations — the description covers what the tool returns conceptually and how to request everything. No return-value explanation is needed given the absence of an output schema and the clear topic enumeration.

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% and the enum values are fully self-describing, so the schema already does the work. The description restates the same topic names and the 'all' fallback, adding no format or behavioral detail beyond the schema's own 'Defaults to all.' Baseline 3 applies.

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 ('Show what SubscriptionFlow does') and enumerates the concrete content areas (features, industries, integrations, benefits, pricing). The sibling list (contact, demo booking, connection status) makes clear this is the product-information tool, with no ambiguity about which one answers 'what is this product' questions.

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 gives one operational instruction — use topic "all" to retrieve everything at once — which is a usage hint for the parameter, not a when-to-use-this-tool-vs-alternatives statement. There is no explicit context about which user questions should route here versus to sf_demo_booking or sf_connection_status; the usage is only implied by the topic list.

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