Skip to main content
Glama
Sign In
DaySmart MCP server

DaySmart MCP server

by cotlet-connect
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

daysmart_click

Clicks a numbered element from the last DaySmart page read to interact with controls and complete booking, record, or navigation actions.

Instructions

Click a numbered element on the current DaySmart 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": "daysmart_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.1/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 burden and mostly fails: it doesn't say whether clicking navigates, submits a form, changes application state, or is reversible. The only context given is that the element is on 'the current page', which hints at statefulness but doesn't explain consequences.

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

Conciseness4/5

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

One short sentence with no wasted words and the action front-loaded. It is efficient, though the extreme brevity is under-specification rather than ideal density.

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

Completeness2/5

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

For an interactive UI-mutating tool with no annotations and no output schema, the description is too thin: it omits what happens after the click, whether state changes persist, how failures surface, and the read-before-click dependency.

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 parameter is documented as 'Element number from the last read'. The description's phrase 'numbered element' is consistent with that but adds no new meaning, so the 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 ('Click') and resource ('a numbered element on the current DaySmart page'), which is clearly distinct from siblings like daysmart_type and daysmart_read. It does not explicitly name an alternative, but the action itself is unambiguous.

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: 'from the last read' in the schema suggests a prerequisite read step, but the description never states when to click versus when to use daysmart_type or daysmart_open, nor any conditions where clicking is inappropriate.

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