Skip to main content
Glama

How to start using All4Clinic

get_signup_info
Read-only

How a clinic starts with All4Clinic: free trial length, where to create the account (link with the chosen plan when given) and, once the account exists, the path to the first appointment step by step (first patient, first appointment, clinic phone, professionals' working hours, team, WhatsApp), each with where it is in the system and its guide link. Working hours do not hide free slots on the agenda. Use it also for "I created the account, now what?". Creates nothing: the person signs up and does each step in the system.

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

Input Schema

NameRequiredDescriptionDefault
planNoOptional plan key from list_plans, to get the sign-up link already on that plan.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description adds real context by stating 'Creates nothing: the person signs up and does each step in the system' and by clarifying that working hours do not hide free slots on the agenda. That is genuine behavioral content beyond the annotations, though the return shape itself is only loosely described.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first clause, but the opening sentence is a run-on packing trial length, sign-up link, and a seven-item parenthetical step list. The caveats that follow are useful but the structure could be split for scannability.

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 simple, single-optional-parameter read-only tool with no output schema, the description covers what the tool returns (trial length, sign-up link, each onboarding step with its system location and guide link) and its non-mutating nature. Nothing an agent needs to call it correctly 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?

There is a single optional 'plan' parameter with 100% schema description coverage, including its own reference to list_plans. The description only alludes to it ('link with the chosen plan when given'), so the schema does the real work — 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 names a specific resource and scope: onboarding information for a clinic, including trial length, sign-up link, and the step-by-step path to a first appointment. It is clearly different from siblings like search_help or get_faq, though the phrasing is dense and buried in a long sentence.

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?

It offers one concrete trigger ('I created the account, now what?') and implies use at clinic sign-up, but never states when NOT to use it or which sibling to prefer for general product questions (get_faq, search_help). Usage is implied rather than routed.

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