Skip to main content
Glama
SimplyWise Cost Estimator MCP Server

SimplyWise Cost Estimator MCP Server

simplywise_cost_estimator_close

Close the SimplyWise Cost Estimator browser session after finishing work to stop credit usage and end the active session.

Instructions

Close the SimplyWise Cost Estimator browser session when the work is done, so credits stop running.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations at all, the description carries the full disclosure burden, and it does add a valuable non-obvious consequence: credits stop accruing once the session is closed, which motivates the call. It does not say whether closing discards unfinished estimator state, whether it is idempotent, or what happens if invoked with no active session, which are the traits an agent most needs for a teardown call.

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 sentence with the action front-loaded and the reason trailing it. No redundant restatement of the tool name and nothing to trim.

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 zero-parameter, no-output-schema teardown tool, the definition covers the action, the timing, and the cost rationale, which is enough to invoke it correctly. Only edge-case behavior (double-close, missing session) is left unstated, a minor gap at this complexity level.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate beyond what the empty schema already shows. Baseline 4 applies for a no-parameter tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb plus resource ('Close the SimplyWise Cost Estimator browser session'), which is unmistakably the teardown counterpart to the sibling open/click/type/read tools. An agent can tell this is the session-termination action without consulting any schema.

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?

Gives an explicit trigger condition: 'when the work is done.' This tells the agent the lifecycle point at which to call it. It stops short of naming a hard alternative or exclusion (e.g. what to do if no session exists), but the usage context is unambiguous.

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