Skip to main content
Glama
Treatwell MCP Server

Treatwell MCP Server

treatwell_read

Reads the current Treatwell page, returning its text plus numbered buttons, links, and fields so agents can identify what to click or fill next.

Instructions

Read the current Treatwell 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": "treatwell_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

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 disclosure burden. It usefully reveals the return shape (text plus numbered interactive elements), which explains how indices for sibling tools arise, but says nothing about read-only safety, size/truncation limits, or whether the numbering is stable between calls.

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 sentence, front-loaded with the verb and target, then the payload list. No filler or redundancy.

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 simple one-optional-parameter read tool with no output schema, the description covers purpose and rough return contents. It is still missing what an agent most needs here: how the numbering works and whether indices remain valid after another read or an action.

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 coverage is 100% and the single optional 'element' parameter is documented there as 'Read only inside this element.', so the schema already does the work. The description never mentions scoping to an element, so it adds no meaning beyond the schema.

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 and resource ('Read the current Treatwell page') and enumerates what comes back: text, numbered buttons, links and fields. That distinguishes it from the mutating siblings (click, type, open, close) without naming them, but the contrast is left implicit.

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 by the word 'Read' – an agent can infer it should call this to inspect page state before clicking or typing. There is no explicit when-to-use/when-not-to-use statement and no guidance on how it pairs with treatwell_click or treatwell_status.

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