Skip to main content
Glama

Virtual Assistant Capital

Compare cost with a local hire

compare_cost_with_local_hire
Read-onlyIdempotent

Calculates the monthly cost of a local hire from an hourly wage, weekly hours and an optional employer on-cost percentage, and shows it beside the Virtual Assistant Capital plan with the closest hours. Uses only the numbers supplied; treats the wage as US dollars.

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": {
      "local_hourly_wage": "<local_hourly_wage>",
      "hours_per_week": "<hours_per_week>"
    },
    "name": "compare_cost_with_local_hire"
  }
}

Input Schema

NameRequiredDescriptionDefault
hours_per_weekYesHours per week needed.
local_hourly_wageYesHourly wage of the local hire, in US dollars.
employer_cost_percentNoOptional employer on-costs (payroll taxes, benefits) as a percentage of wages. Defaults to 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, closed-world, non-destructive behavior, and on top of that the description discloses that it uses only the supplied numbers and treats the wage as US dollars, and that the plan match is chosen by closest hours. The remaining gap is that the exact returned fields are only gestured at ('shows it beside…').

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?

A single compact sentence that front-loads the computation and puts the comparison and currency assumption at the end; no filler. It could be split for readability, but every clause carries information.

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 three-parameter read-only calculation tool with full schema coverage and no output schema, the description supplies the computation logic, the currency assumption, and the plan-matching rule, which is enough for an agent to call it confidently. What the response actually contains is described only loosely, which is the one shortfall.

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 coverage is 100%, so a baseline of 3 applies, but the description adds real meaning beyond the schema by explaining that employer_cost_percent is optional on-costs folded into a monthly figure and that hours drive which plan is selected for comparison. This clarifies the relationship between parameters rather than restating them.

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 gives a specific verb and resource ('Calculates the monthly cost of a local hire') plus the exact inputs (hourly wage, weekly hours, on-cost percentage) and the comparison output against the VA Capital plan. It is clear what the tool does, though it never names a sibling such as get_plans_and_pricing to draw an explicit boundary.

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 implied rather than stated: an agent can infer this is the tool for 'what would a local hire cost versus a VA' questions, but there is no explicit 'use this when…' clause, no exclusions, and no reference to when get_plans_and_pricing would be the better call for pure plan pricing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources