Skip to main content
Glama

get_audit_fee_benchmark

Read-only

Use when benchmarking audit costs, evaluating auditor proposals, or preparing an audit committee RFP. Audit fee benchmarks — total fees and fees as a percentage of revenue by company revenue band and auditor tier (Big 4 vs national vs regional). Source: Audit Analytics public aggregate data. Used by CFOs and audit committees in auditor RFPs and fee negotiations. $0.02 USDC per call.

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": {
      "annual_revenue_usd": "<annual_revenue_usd>"
    },
    "name": "get_audit_fee_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
industryNo
auditor_tierNo
annual_revenue_usdYesAnnual revenue in USD, e.g. 50000000 for $50M

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds real value beyond them by naming the data source (Audit Analytics public aggregate data) and disclosing a per-call price of $0.02 USDC, but it says nothing about behavior on an out-of-range revenue, an unsupported industry, or how sparse the results may be for narrow bands.

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 front-loaded with the trigger condition, then the data content, then source and price — a sensible order with no fluff. The 'Used by CFOs and audit committees' sentence is mild marketing that only marginally reinforces the usage section.

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?

With no output schema, the description does well to state the returned metrics and segmenting dimensions, and the price is disclosed. However, for a three-parameter tool it leaves a full parameter (industry) undocumented and does not say whether revenue values are dollars or thousands or what happens when a tier/industry combination has no data.

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 low at 33% — only annual_revenue_usd is documented — so the description has to carry more weight. It does clarify the auditor_tier enum semantics (Big 4 vs national vs regional) and the revenue-band dimension, but the industry parameter is never mentioned in either the schema or the description, leaving its valid values and effect entirely opaque.

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 specific resource (audit fee benchmarks) and states exactly what the payload contains: total fees and fees as a percentage of revenue broken out by revenue band and auditor tier. That distinguishes it from the other benchmark siblings (e.g. get_cac_benchmark, get_earnings_quality_benchmark) by domain, though it never explicitly contrasts itself with any named alternative.

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?

It gives concrete trigger scenarios — benchmarking audit costs, evaluating auditor proposals, preparing an audit committee RFP — which is clear when-to-use guidance. It does not state when to avoid the tool or what to use instead (e.g. for non-audit professional fees), so it stops short of full routing instructions.

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