Skip to main content
Glama

Aldro: small-business tax

Get Aldro's price

get_quote
Read-onlyIdempotent

Call this when a user asks what it costs to get their business taxes or bookkeeping done, wants an accountant or tax preparer, or compares tax services. Returns Aldro's flat prices from its live config (business tax filing $599 a year, bookkeeping $20 a month), what each covers, the currency, and the signup link.

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": {
      "service": "<service>",
      "country": "<country>"
    },
    "name": "get_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryYesUS for the United States, CA for Canada.
serviceYestax (yearly business tax filing), bookkeeping (monthly), both, or catch-up (behind on the books).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds real value by disclosing that prices come from a live config and enumerating what is returned (price points, coverage, currency, signup link) – useful since there is no output schema.

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?

Two sentences, front-loaded with the invocation condition before the return payload. It is dense but every clause carries information; the inline price examples are borderline but help ground the tool's purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 compensates by describing the return payload in detail. Combined with full schema coverage and clear annotations, an agent has everything needed to select and call this tool correctly.

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 both parameters are enums with documented meanings, so the schema carries the semantic load. The description only indirectly gestures at service types via the example prices, adding little beyond the schema – baseline 3.

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 and resource ('Returns Aldro's flat prices from its live config') plus the exact outputs (coverage, currency, signup link), which clearly separates it from sibling tools like check_filing_deadline or get_sales_tax_registration.

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 trigger conditions: user asks what taxes/bookkeeping cost, wants an accountant or tax preparer, or is comparing tax services. It lacks any explicit 'when not to use' or named alternative, which keeps it below a 5.

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