Skip to main content
Glama
SimplyWise Cost Estimator MCP Server

SimplyWise Cost Estimator MCP Server

simplywise_cost_estimator_click

Selects a numbered element on the current SimplyWise Cost Estimator page to edit or interact with estimate fields, using the element number from the last read.

Instructions

Click a numbered element on the current SimplyWise Cost Estimator 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": "simplywise_cost_estimator_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?

No annotations are supplied, so the description carries the full behavioral burden. It does not say whether the click navigates or mutates page state, what happens with a stale or invalid element number, whether the element index set becomes invalid after the click (requiring a re-read), or whether authentication/session state matters—all critical for an action tool.

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, front-loaded sentence with no filler and no redundancy. It is efficient rather than verbose, though the brevity is partly under-specification rather than disciplined economy.

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 a page-action tool with no annotations and no output schema, the definition should disclose preconditions (a prior read must have produced the numbering) and consequences (state change, need to re-read). Neither is present, so an agent must infer the entire read-click-read loop.

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?

The single parameter is fully documented in the schema ('Element number from the last read', minimum 1), so coverage is 100% and the baseline is 3. The description adds no meaning beyond the schema, such as whether numbering is stable across reads or whether it is 1-based per the schema's minimum.

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 a specific target ('a numbered element on the current SimplyWise Cost Estimator page'), which is distinguishable from the sibling 'type' (text entry) and 'read' (enumerate elements). It stops short of explicitly naming or contrasting those siblings, so it is clear but not differentiated by routing language.

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: 'current page' suggests a page must already be open, and the schema's 'Element number from the last read' hints at a read-then-click sequence. There is no explicit when-to-use vs. 'type', no statement of prerequisites, and no guidance on what to do afterward.

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