ClinicSense MCP Server

clinicsense_read

Reads the active ClinicSense page to return its text and numbered buttons, links, and fields, with an optional element ID to limit reading to a specific section.

Instructions

Read the current ClinicSense page: its text and numbered buttons, links and fields.

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

Input Schema

Name	Required	Description	Default
`element`	No	Read only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Nov 15, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. The verb 'Read' plus the enumerated return contents (text, numbered buttons, links, fields) communicates a non-mutating snapshot and roughly what comes back, which is meaningful context. However, it says nothing about behavior when no page is open, truncation/size limits, or freshness of the snapshot.

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?

A single sentence with zero filler, front-loading the verb and resource before the returned content. Nothing could be cut without losing information.

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?

This is a low-complexity read tool with one fully documented optional parameter and no output schema, so the description need not explain return structure in depth. It does name the token kinds returned, but omits what the numbering means for follow-up clicks and what happens on an unopened page — small gaps for a tool this simple.

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 optional 'element' parameter is already documented as 'Read only inside this element.' The description mentions 'numbered buttons, links and fields' but never connects those to the element-scoping parameter, so it adds no meaning beyond the schema. 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?

States a specific verb ('Read') and a specific resource ('the current ClinicSense page'), then enumerates the content returned: text, numbered buttons, links, fields. This is clearly distinguishable from click/type/close siblings, though it never names them explicitly.

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 only implied: 'the current page' hints that a page must already be open and that this is a snapshot/inspection step rather than an action. There is no explicit statement of when to prefer this over clinicsense_status or clinicsense_guide, nor any precondition or exclusion.

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

Deploy Server