Skip to main content
Glama
SimplyWise Cost Estimator MCP Server

SimplyWise Cost Estimator MCP Server

simplywise_cost_estimator_read

Read the active SimplyWise cost estimator page to capture its text and numbered buttons, links, and fields for review or automation.

Instructions

Read the current SimplyWise Cost Estimator 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": "simplywise_cost_estimator_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It correctly signals a read/snapshot operation and describes the returned content shape (text plus numbered interactive elements), but says nothing about whether numbering is stable across reads, whether large pages are truncated, or what happens if no page is open.

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 front-loaded sentence with no filler, and the colon construction puts the returned content exactly where a caller needs it.

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?

For a one-optional-parameter read tool with no output schema, the description covers target and returned content adequately. The remaining gap is behavioral: the relationship between the 'numbered buttons' and the element index, and truncation behavior for large pages.

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?

One optional parameter at 100% schema coverage, so the schema already explains 'element' as a scoped read. The description never mentions the element 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 SimplyWise Cost Estimator page), then enumerates what the read returns: text, numbered buttons, links and fields. That enumeration implicitly separates it from siblings like click and type, though it never names them.

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 the page must already be open and that this is the inspection step preceding click/type. There is no explicit when-to-use, when-not-to-use, or named alternative among the click/type/open/status siblings.

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