Skip to main content
Glama

FlowVolt

by io.github.Larshiensch99

Server Details

Cold engine for B2B founders. Detects buying signals, drafts outreach, books qualified meetings.

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Last Tested
Transport
Streamable HTTP
URL

Available Tools

3 tools
addAddAInspect

Adds two numbers and returns the sum.

ParametersJSON Schema
NameRequiredDescriptionDefault
aYes
bYes

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does state the core behavior: addition and returning a sum. It does not address edge cases or output shape, but for a pure arithmetic operation the main behavior is transparent.

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?

The description is a single eight-word sentence with no filler. The action and result are immediately front-loaded.

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 two-operand arithmetic tool, the description plus input schema cover what to pass and what to expect. It omits explicit return format and error behavior, but the simplicity of the operation makes those omissions minor.

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?

The schema has no per-parameter descriptions, and the description only says 'two numbers' without naming a and b or adding constraints. However, addition is commutative, so the missing role differentiation is not a practical issue.

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?

The phrase 'Adds two numbers and returns the sum' uses a specific verb and outcome. It clearly identifies the operation and is easily distinguishable from echo and server_time.

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?

There is no explicit when-to-use or alternatives statement. The intended use is implied by the description and tool name, but selection guidance is left to obviousness rather than being stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

echoEchoAInspect

Echoes the provided text back to the caller.

ParametersJSON Schema
NameRequiredDescriptionDefault
textYesText to echo back

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden. It accurately conveys that the tool returns the supplied text unchanged, which fully covers the relevant behavior for this trivial tool. It does not need to disclose side effects because the behavior itself implies none.

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?

The description is a single sentence with no filler, front-loading the action immediately. Every word contributes to understanding the tool's purpose.

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 one-parameter tool with no output schema and no annotations, the description is complete. It states the operation, the input, and the result ('back to the caller'), leaving nothing material unknown to the agent.

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%, so the schema already fully documents the single 'text' parameter. The description adds no new parameter-meaning detail; it merely restates the concept, which earns the baseline score.

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 uses a clear verb ('Echoes') and resource ('the provided text') and makes the tool's function immediately obvious. It does not explicitly differentiate from siblings, but the purpose is unambiguous enough that an agent would not confuse it with 'add' or 'server_time'.

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?

Usage is implied: an agent would use this when it needs to echo text back. However, the description gives no explicit guidance about when to choose this tool over alternatives or any exclusions, leaving the context entirely implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

server_timeServer timeAInspect

Returns the current server time (ISO 8601, UTC).

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses the return format (ISO 8601), the timezone basis (UTC), and the fact that the value is the current server time, which is sufficient given the tool's trivial behavior.

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?

The description is one short, front-loaded sentence with no filler. Every word adds meaning.

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 parameterless tool with no output schema, the description fully covers what an agent needs to know: the action, the result, the format, and the timezone.

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 has zero parameters, so the schema imposes no documentation burden. The description adds no parameter-specific detail, but none is needed.

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?

The description uses a specific verb ('Returns') and resource ('current server time') plus format details (ISO 8601, UTC). This clearly distinguishes it from the sibling tools add and echo.

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?

The description makes the tool's purpose explicit and implies it is used whenever the server's current time is needed. It does not explicitly mention when not to use it or name alternatives, but the sibling tools are unrelated to time retrieval.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 26 tool updates
    • Addedadd
    • Removedbook_meeting
    • Removedcalculate_payback
    • Removeddiscover_business
    • Addedecho
    • Removededit_message
    • Removedenqueue_lead
    • Removedfind_leads
    • Removedflowvolt_freetrial
    • Removedflowvolt_send_trial
    • Removedget_funnel
    • Removedget_pipeline
    • Removedget_receipts
    • Removedget_replies
    • Removedget_started
    • Removedget_subscription_status
    • Removedlist_meetings
    • Removedmanage_billing
    • Removedpause_engine
    • Removedpreview_message
    • Removedquote
    • Removedresume_engine
    • Removedsearch_people
    • Addedserver_time
    • Removedset_goal
    • Removedsubscribe
  2. 2 tool updates
    • Addedflowvolt_freetrial
    • Addedflowvolt_send_trial
  3. 12 tool updates
    • Addedcalculate_payback
    • Addeddiscover_business
    • Addededit_message
    • Changedfind_leads2 fields changed
      • changedInput schema / properties / email / description
        Previous value: -"Optional. The user's work email — if provided on a free_trial call, we create a provisional tenant and mail them a follow-up. Without it, free_trial still works but no follow-up email."New value: +"Optional. The user's work email."
      • changedInput schema / properties / quote_id / description
        Previous value: -"A quote_id returned by the quote() tool. Must be a free_trial or topup plan. Example: 'q_trial_abc12345'"New value: +"A quote_id returned by quote() or discover_business(). Must be free_trial or topup."
    • Changedget_started3 fields changed
      • addedInput schema / properties / company
        Added value: +{
+  "description": "The user's business name if known. Optional.",
+  "type": "string"
+}
      • removedInput schema / properties / context
        Removed value: -{
-  "description": "Anything the user mentioned about their company, role, or what they're trying to do. Example: 'I run a B2B SaaS in Holland selling to fintechs.' Optional but improves the response.",
-  "type": "string"
-}
      • addedInput schema / properties / name
        Added value: +{
+  "description": "The user's first name if known. Optional.",
+  "type": "string"
+}
    • Changedget_subscription_status2 fields changed
      • changedInput schema / properties / email / description
        Previous value: -"Optional. The email used at Stripe Checkout. Only needed if you're not authenticated with an MCP token."New value: +"Stripe Checkout email if not authenticated."
      • addedInput schema / properties / name
        Added value: +{
+  "description": "User's first name if known.",
+  "type": "string"
+}
    • Changedmanage_billing2 fields changed
      • changedInput schema / properties / email / description
        Previous value: -"Optional. The email used at Stripe Checkout. Only needed if you're not authenticated with an MCP token."New value: +"Stripe Checkout email if not authenticated."
      • addedInput schema / properties / name
        Added value: +{
+  "description": "User's first name if known.",
+  "type": "string"
+}
    • Changedpause_engine2 fields changed
      • changedInput schema / properties / email / description
        Previous value: -"Optional. Stripe-Checkout email if not authenticated."New value: +"Stripe Checkout email if not authenticated."
      • addedInput schema / properties / name
        Added value: +{
+  "description": "User's first name if known.",
+  "type": "string"
+}
    • Addedpreview_message
    • Changedquote3 fields changed
      • addedInput schema / properties / company
        Added value: +{
+  "description": "Business name if known.",
+  "type": "string"
+}
      • addedInput schema / properties / name
        Added value: +{
+  "description": "User's first name if known.",
+  "type": "string"
+}
      • changedInput schema / properties / use_case / description
        Previous value: -"Natural language description of who the user wants to sell to. Example: 'I sell B2B AI tooling to Dutch fintech CFOs hiring their first sales lead. Find me 25 of them with the receipt of why they're in-market right now.'"New value: +"Natural language description of the customers the user wants to reach."
    • Changedresume_engine2 fields changed
      • changedInput schema / properties / email / description
        Previous value: -"Optional. Stripe-Checkout email if not authenticated."New value: +"Stripe Checkout email if not authenticated."
      • addedInput schema / properties / name
        Added value: +{
+  "description": "User's first name if known.",
+  "type": "string"
+}
    • Changedsubscribe1 field changed
      • changedInput schema / properties / quote_id / description
        Previous value: -"A quote_id from quote() with plan=solo, pro, or scale. Example: 'q_pro_abc12345'"New value: +"A quote_id with plan=solo, pro, or scale."
  4. 4 tool updates
    • Addedget_subscription_status
    • Addedmanage_billing
    • Addedpause_engine
    • Addedresume_engine
  5. 1 tool update
    • Addedsubscribe
  6. 12 tool updates
    • First observedbook_meeting
    • First observedenqueue_lead
    • First observedfind_leads
    • First observedget_funnel
    • First observedget_pipeline
    • First observedget_receipts
    • First observedget_replies
    • First observedget_started
    • First observedlist_meetings
    • First observedquote
    • First observedsearch_people
    • First observedset_goal

Frequently Asked Questions

Discussions

No comments yet. Be the first to start the discussion!

Login with GitHub to comment

Related MCP Connectors

Related MCP Servers

  • signal-prospector

    thomasproject-stack
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables B2B prospecting from natural language: detect buying signals, score leads against ICP, enrich decision-makers, and draft personalized outreach messages via Claude.
    1
    MIT

  • mcp-gtm-suite

    mambalabsdev
    A
    license
    A
    quality
    A
    maintenance
    GTM signal intelligence suite for AI agents. Six tools: hiring signals, tech stack detection, company-to-LinkedIn resolution, ICP scoring, job board scanning, and a combined signals aggregator. Built for outbound sales workflows.
    11
    162
    1
    MIT

  • SignalPipe

    AbYousef739
    A
    license
    Not graded
    quality
    B
    maintenance
    Agentic sales pipeline that detects buying intent from social feeds, scores leads via an AI swarm, and auto-drafts calibrated replies for prospect nurturing.
    216
    MIT
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation5/5

Each tool performs a completely distinct function—numeric addition, text echoing, and time retrieval—with zero overlap in purpose. An agent would never confuse these tools.

Naming Consistency3/5

add and echo are single-word verbs, while server_time is a noun phrase with an underscore, creating a slight inconsistency. The names are readable and lowercase, but the pattern is not uniformly maintained.

Tool Count3/5

Three tools falls within the acceptable range, but the tools are so unrelated that the set feels like a random collection rather than a purposeful server. A more focused server would either have more tools around a coherent domain or make a clearer case for each tool.

Completeness2/5

There is no identifiable domain or workflow to assess coverage against; the tools are disconnected and provide only trivial operations. As a usable server for any real task, it offers almost no meaningful capability surface.

Resources