Skip to main content
Glama

SubscriptionFlow

Find my SubscriptionFlow instance

sf_find_instance
Read-only

Given a work email, start the enumeration- and timing-safe instance lookup. For privacy the response is deliberately generic and constant — it never confirms or denies whether an account exists; if a match is found, instructions are sent to that email. 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_find_instance"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesA work email address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint, yet the description adds real behavioral detail beyond them: the lookup is enumeration- and timing-safe, the response never confirms or denies an account, and instructions are emailed on a match. It stops short of stating rate limits, throttling, or what the caller should do after a generic response.

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 compact sentences, front-loaded with the input and the action, then the privacy-relevant behavior. No redundant restatement of the name or annotations; every clause carries information.

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 one-parameter, no-output-schema tool, the description covers input, safety posture, and the shape of the response (generic and constant). It could add what the agent should tell the user after a generic response, but nothing essential to correct invocation is missing.

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?

Single required parameter with 100% schema coverage including format=email and length bounds, so the schema carries the semantics. The description's contribution is limited to reiterating 'work email', adding little beyond the field's own description.

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?

States a specific verb+resource: starts an instance lookup for a work email, in the context of finding 'my SubscriptionFlow instance'. Clear enough to act on, though it does not explicitly contrast itself with siblings like sf_connection_status, so an agent must infer the boundary.

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?

The trigger condition is implied by 'Given a work email' and the intent is implied by the title (user has lost their instance), but there is no explicit when-to-use/when-not guidance nor any named alternative for cases where the user already knows their instance or has no work email.

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