Skip to main content
Glama
Sign In
ClinicSense MCP Server

ClinicSense MCP Server

by cotlet-connect
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

clinicsense_click

Clicks a numbered element on the current ClinicSense page to navigate or act on it. Use the element number from the last page read to target the correct control.

Instructions

Click a numbered element on the current ClinicSense page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "element": "<element>"
    },
    "name": "clinicsense_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden but says only that a click occurs. It does not disclose possible navigation or state changes, whether another read is needed afterward, or what happens when an element number is invalid or stale.

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 single sentence is short, direct, and front-loaded with the action and target. There is no redundant or unnecessary wording.

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?

Together with the schema, the description is sufficient for a basic invocation on a freshly read page. However, for a potentially state-changing interaction with no annotations or output schema, the lack of side-effect, navigation, and stale-element guidance leaves meaningful operational gaps.

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 schema already documents that element is an integer of at least 1 obtained from the last read. The description's "numbered element" wording adds little parameter meaning beyond that, so the baseline score 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 specifies the action ("Click"), target ("a numbered element"), and scope ("the current ClinicSense page"). It does not explicitly differentiate this tool from sibling actions such as reading or typing.

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 wording implies that the tool acts on an element already enumerated on the current page. It provides no explicit read-first workflow, stale-number guidance, or when-not-to-use guidance, although the schema does connect the element number to the last read.

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

Deploy Server

Other Tools