Skip to main content
Glama

Tiquiz Quiz Funnel

Check CRM connections

get_connections
Read-onlyIdempotent

Check the health of the account's integrations (Systeme.io API keys, GoHighLevel sub-accounts, webhooks): active, paused or disconnected, and the last error. With quiz_id: where this quiz really sends its leads, the exact tags Tiquiz will apply, what is missing for them to be applied, and (check_tags) which of those tags do not exist yet in Systeme.io or GoHighLevel. Use it for 'are my leads reaching my CRM with the right tag?'. Read only: it creates nothing. It never returns an API key, token or webhook secret.

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": "get_connections"
  }
}

Input Schema

NameRequiredDescriptionDefault
quiz_idNoCheck the connection this quiz really sends its leads to, and its tags. Omit for every connection of the account.
check_tagsNoWith quiz_id: ask Systeme.io or GoHighLevel which of the expected tags exist. Read only, nothing is created.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: 'it creates nothing' and, importantly, 'It never returns an API key, token or webhook secret', which tells the agent what sensitive data will be absent from the response. It stops short of describing rate limits, pagination, or failure modes beyond 'the last error'.

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?

It is front-loaded with the core purpose and then branches cleanly into the quiz_id and check_tags behaviors. The parenthetical integration list is dense but useful; the only mild cost is length in the opening sentence.

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?

There is no output schema, so the description must carry the return-value burden, and it does: status values (active, paused, disconnected), last error, real destination, applied tags, and missing tags. For a two-parameter, read-only diagnostic tool, nothing essential is left for the agent to guess.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by explaining that quiz_id reveals the real destination of a quiz's leads plus the exact tags applied and what is missing for them to apply. It also clarifies that check_tags queries the provider for tag existence rather than creating anything.

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 names a specific verb and resource ('Check the health of the account's integrations') and enumerates the integration types covered (Systeme.io API keys, GoHighLevel sub-accounts, webhooks). It also distinguishes the two operating modes, account-wide vs. quiz-scoped, so an agent can tell exactly what this tool returns.

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?

It gives an explicit intent phrase, 'are my leads reaching my CRM with the right tag?', and states that omitting quiz_id widens the scope to every connection of the account. It does not explicitly name a sibling tool or a when-not-to-use condition, which keeps it below 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