Skip to main content
Glama
Sign In

Callvu

by com.callvu
OverviewDiscussionsAdmin

Estimate the cost of doing nothing

estimate_cost_of_doing_nothing
Read-onlyIdempotent

Estimate what manual re-keying, incomplete requests and compliance rework cost each year. Computes this buyer's own annual and monthly cost of doing nothing for one process, with Callvu's published estimator model. Ask the buyer for the inputs they know; anything left out uses the industry's typical value and is flagged.

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": {
      "vertical": "<vertical>"
    },
    "name": "estimate_cost_of_doing_nothing"
  }
}

Input Schema

NameRequiredDescriptionDefault
ai_levelNoWhere AI stands on this process: none, pilot or production.
verticalYesA vertical slug, name or alias, for example "banking", "Home lending" or "mortgage". Case-insensitive.
manual_shareNoShare of requests handled manually, 0 to 1.
abandoned_shareNoShare abandoned before completion, 0 to 1.
incomplete_shareNoShare that arrive incomplete or need rework, 0 to 1.
value_per_requestNoAverage value per request, in US dollars.
requests_per_monthNoRequests or cases per month for the process.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, non-destructive local computation, so the safety profile is covered. The description adds genuinely non-obvious behavior: only the buyer's known inputs are used and any omitted inputs fall back to industry-typical values that are flagged in the result. It omits failure behavior, e.g., how an unrecognized vertical is handled.

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?

Three sentences, front-loaded with the deliverable (annual and monthly cost) before the mechanics. No filler, no restatement of the title, and the fallback rule arrives last where it is most useful.

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?

With no output schema, the description still names the return shape (annual and monthly cost, with flagged defaults) which is enough for a stateless single-process estimator. Minor gaps remain around the vertical resolution failure path and precision/currency, but nothing an agent needs to call it correctly is missing.

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?

Schema description coverage is 100%, which sets a baseline of 3. The description adds real meaning beyond the schema by explaining the contract for the six optional inputs: supply what the buyer knows, everything else defaults to an industry-typical value and is surfaced as flagged, which tells the agent how to sequence data collection and what the defaults imply.

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 computation (annual and monthly cost of doing nothing) for a scoped unit (one process) using a named model (Callvu's published estimator). It enumerates the cost drivers included (manual re-keying, incomplete requests, compliance rework), so the agent knows exactly what is being estimated. It never contrasts itself with siblings such as compare_alternatives or get_pricing_model, so differentiation is left to inference.

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 concrete invocation guidance: ask the buyer for the inputs they know, and omit what they don't. It does not say when NOT to use it or which sibling to pick for adjacent needs (e.g., pricing vs. comparing alternatives), but the usage context is clear and actionable.

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

All Callvu toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources