Skip to main content
Glama
SimplyWise Cost Estimator MCP Server

SimplyWise Cost Estimator MCP Server

simplywise_cost_estimator_guide

Guides you through SimplyWise Cost Estimator screens and sign-in link so you can draft and adjust estimates, line items, discounts, fees, and tax.

Instructions

How to work in SimplyWise Cost Estimator (estimates, line items, discounts, fees and tax): its screens and the sign-in link. Call this first.

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

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in SimplyWise Cost Estimator, in your words.

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?

With no annotations supplied, the description carries the full behavioral burden, and it does convey that this is informational (a how-to over screens and a sign-in link) rather than an action on data. However, it never states that it is side-effect free, whether the sign-in link is returned as output, or what form the guidance takes, so an agent must infer the safe-read profile from the word 'guide' alone.

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?

It is two compact clauses with no filler, and the topical scope is front-loaded. The key directive 'Call this first' is placed at the very end, which is a minor structural miss given it is the single most important instruction, but the description is short enough that nothing gets lost.

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?

The tool is simple (one optional parameter, no output schema, no annotations), so the description does not need much. What is missing is any statement of what the agent receives back or how to act on the 'sign-in link' once obtained, which matters because this is billed as the mandatory first step before other tools.

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 there is a single optional 'task' parameter already documented as 'What you want done in SimplyWise Cost Estimator, in your words.' The description adds no meaning about how the task shapes the returned guidance or whether the parameter is optional. Per the high-coverage baseline, 3 is the correct score.

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?

The description names a concrete subject (SimplyWise Cost Estimator) and enumerates the domain concepts it covers: estimates, line items, discounts, fees and tax, plus 'its screens and the sign-in link.' That is enough to tell it apart from the action siblings (open, click, type, read, status, close), which are operational verbs. The phrasing 'How to work in...' is slightly indirect about whether it returns guidance or performs an action, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Call this first' is an explicit ordering directive that tells the agent when to reach for this tool relative to every sibling. It does not spell out a when-not condition, but for an onboarding/guide tool the primary alternative is simply 'after this, use the operational tools,' which is strongly implied by the ordering instruction.

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