Skip to main content
Glama

SubscriptionFlow

Check SubscriptionFlow sign-in

sf_connection_status
Read-only

Check whether this connection is signed in to a SubscriptionFlow account. Call it when the user asks for their own SubscriptionFlow data (customers, subscriptions, invoices, payments, billing, reports) or for a change, and no account tools are listed. Right now the connection is not signed in; the result says how to reconnect. 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_connection_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so 'Read-only' adds nothing new. What does add value is the disclosure that the connection is currently not signed in and that the result explains how to reconnect — genuine state and response-context information the annotations cannot convey. This is meaningful behavior beyond the structured fields.

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 purpose, then trigger, then current state. Nearly every clause earns its place; the trailing 'Read-only' is the one redundant element since the annotations and the nature of a status check already make that clear.

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, zero-output-schema status probe, the description supplies everything an agent needs: what it checks, the precise condition for calling it, the present state, and what the response will contain. Nothing material 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 takes zero parameters, so there are no argument semantics to explain and the baseline of 4 applies. The description correctly spends no space on parameters and instead covers invocation conditions.

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?

Uses a specific verb and resource: 'Check whether this connection is signed in to a SubscriptionFlow account.' It also carves out its slot relative to account tools via the 'no account tools are listed' condition, so an agent can tell it apart from the sibling sf_* tools without opening a schema. It stops short of a 5 only because the differentiation is conditional rather than naming the alternatives directly.

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

Usage Guidelines4/5

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

Explicitly states the trigger: the user asks for their own SubscriptionFlow data (enumerated domains) or for a change, and no account tools are listed. The inverse case (account tools exist, use those instead) is strongly implied by that precondition. It does not spell out what to do after a positive sign-in result, which keeps it from a 5.

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