ClinicSense MCP Server

clinicsense_open

Opens a ClinicSense page in your signed-in Cloud Browser to manage appointments, wait lists, payments, and financial reports; defaults to app.clinicsense.com.

Instructions

Open a ClinicSense page in your signed-in Cloud Browser (default https://app.clinicsense.com) to work with appointments, wait lists, payments and financial reports.

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

Input Schema

Name	Required	Description	Default
`url`	No	Page to open. Default: https://app.clinicsense.com

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Nov 15, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the full burden; it usefully discloses that the browser is 'signed-in', telling the agent an authenticated session is required. It does not say whether navigation replaces the current page (potentially discarding state), whether it waits for load, or whether page content is returned or must be fetched via clinicsense_read.

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?

One front-loaded sentence with no filler: verb, resource, environment, default value, and scope of use. Nothing redundant or buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-optional-parameter navigation tool with no output schema, the essentials are present, but the relationship to the read/click/type/close siblings is left implicit, and it is unclear whether the opened page's content is returned or requires a follow-up read call.

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 the single 'url' parameter is documented with its default, so the schema already does the work. The description repeats the same default URL rather than adding constraints such as relative-path acceptance or allowed domains.

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?

Names a specific verb ('Open') and a specific resource ('a ClinicSense page in your signed-in Cloud Browser'), plus the task domains it unlocks (appointments, wait lists, payments, financial reports). It is distinguishable from siblings like clinicsense_read or clinicsense_click by the navigation framing, though it never explicitly contrasts itself with them.

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?

Implies when to use it via the listed task domains, so an agent can infer this is the entry point before reading/clicking/typing. There is no explicit when-not guidance, and it does not mention clinicsense_close as the counterpart or state whether opening is required before other tools work.

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

Deploy Server