Skip to main content
Glama

SubscriptionFlow

Show a contact form

sf_contact_form
Read-only

Display an interactive form for getting in touch with the SubscriptionFlow team. The form collects a name, work email, company, optional phone number and a message, and submits them through sf_contact.

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_contact_form"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/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 safety is covered. The description adds real context beyond them: this renders an interactive form, enumerates what it collects, and hands submission off to sf_contact — consistent with the read-only annotation since displaying the form mutates nothing. It stops short of saying what the caller receives or whether the user must complete the form themselves.

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 sentences, front-loaded with the primary action, then the field list and submission path. Every clause carries information; there is no filler.

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 no-parameter, no-output-schema display tool with annotations covering the safety profile, the description covers purpose, contents, and downstream submission. Minor omission: it does not clarify what the calling agent should do after the form is rendered or what is returned.

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 the baseline is 4 and the schema has nothing to explain. The description usefully names the fields the form gathers (name, work email, company, optional phone, message), which is information the agent cannot get from the empty schema.

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 ("Display an interactive form for getting in touch") and immediately scopes it by listing the collected fields. It also names the sibling sf_contact as the submission path, so an agent can tell this renders the form while sf_contact performs the send.

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 mention that entries are "submitted through `sf_contact`" implies the sequencing (show form first, submit second), but there is no explicit when-to-use trigger such as a user asking to contact support, and no when-not guidance against calling sf_contact directly.

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