Skip to main content
Glama

Revenue system audit

run_layer_audit
Read-only

The GTM Vault revenue system audit: eight questions, one per layer of revenue architecture. Called with no answers, it returns the eight questions. Called with all eight answers, it returns the weakest layers, why, the episodes that address them, and a link to the matching stack build.

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": "run_layer_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
answersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds the useful disclosure of what each mode returns, including episodes and a link to a stack build. It does not say whether audit results are persisted, whether the tool is idempotent, or how partial input is handled — meaningful gaps for a two-mode tool with a fixed-length array.

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?

Three sentences, front-loaded with the tool's identity and then the two modes in call order. No filler, though the second and third sentences could be tightened into a single mode/return mapping.

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 takes on the return-value burden and does so for both modes, which is the main thing an agent needs before calling. It stops short of covering partial-input behavior and result persistence, the two remaining questions an agent would have.

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 coverage is effectively 0% at the top level (the nested enum fields do carry their own descriptions), so the description must carry weight. It correctly explains that 'answers' holds one entry per layer and must be complete ('all eight answers'), but it does not restate the holds/partly/breaking scale or the layer_id vocabulary beyond the schema.

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 verb and resource ('revenue system audit') and makes the two operational modes concrete: eight questions returned with no answers, weakest-layer analysis with all eight. An agent can tell it apart from list/search siblings, though it never names an alternative explicitly.

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?

The when-to-call logic is clear and actionable: call empty to retrieve the questions, call with all eight answers to get results. It omits what happens with partial answers (the schema forbids anything but 0 or 8) and gives no guidance on when a sibling like build_stack should be used instead.

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