Skip to main content
Glama

SubscriptionFlow

Contact the SubscriptionFlow team

sf_contact
Read-only

Send a message to the SubscriptionFlow team. Requires a name, work email, company and message; a phone number is optional. Returns a reference id the sender can quote. Nothing submitted is echoed back. 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": {
      "name": "<name>",
      "email": "<email>",
      "company": "<company>",
      "message": "<message>"
    },
    "name": "sf_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFull name of the person getting in touch.
emailYesA work email address.
phoneNoPhone number. Optional.
companyYesCompany or organisation name.
messageYesThe message or enquiry.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior context: it returns a reference id the sender can quote, nothing submitted is echoed back, and the endpoint is public. Those details tell the agent what to expect after the call, which annotations cannot convey.

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?

Four short sentences, front-loaded with the action and followed by requirements, return behavior, and access level. Every sentence carries information, though 'Public, read-only' partly duplicates the annotations and could have been spent on differentiating from sf_contact_form.

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?

There is no output schema, so stating that a reference id is returned and that nothing is echoed back fills an important gap. For a five-parameter submission tool, the definition covers requirements, return value, and access context adequately; the missing piece is only the relationship to the sibling contact-form tool.

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 every parameter carries its own description with length constraints and format. The description only restates which fields are required and that phone is optional, adding no syntax, format, or validation detail beyond the schema. Baseline 3 applies.

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: 'Send a message to the SubscriptionFlow team.' An agent can tell this tool is about initiating contact. However, it does not distinguish itself from the sibling sf_contact_form, which by name appears to serve a very similar purpose, leaving the agent to guess between the two.

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

Usage Guidelines2/5

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

'Public, read-only' hints at the access context, but there is no explicit when-to-use or when-not-to-use guidance and no routing to alternatives. With a sibling named sf_contact_form that plausibly overlaps, the absence of any differentiation statement is a real gap rather than a minor omission.

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