Skip to main content
Glama

ADV IT Performance (AEO websites)

Calculate AEO & Programmatic Landing Page ROI

calculate_aeo_roi
Read-onlyIdempotent

Calculate projected revenue growth, CAC reduction, and payback timeline from deploying ADV Strategy Pro search-to-sale landing pages.

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": {
      "monthly_visitors": "<monthly_visitors>",
      "average_deal_size_usd": "<average_deal_size_usd>"
    },
    "name": "calculate_aeo_roi"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthly_visitorsYesCurrent monthly website visitors across organic and paid channels.
average_deal_size_usdYesAverage customer contract value or order size in USD.
current_conversion_rate_percentNoCurrent lead conversion rate percentage (e.g. 1.5). Default is 1.0%.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this is a read-only, idempotent, non-destructive, closed-world operation, so safety is covered. The description adds which metrics are produced but does not disclose that results are modeled estimates, what benchmark assumptions underpin them, or how the default conversion rate is applied.

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 front-loaded sentence with the verb and outputs up front and no filler. It is appropriately sized, though it leaves plenty of room that could have been used for assumption or return-value context at no cost to brevity.

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 calculator with a fully documented schema and no output schema, the description names the three returned metrics, which is the key missing piece otherwise. It stops short of describing the basis of the projections, but the essential 'what do I get back' signal is present.

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%, with each parameter including a plain-language definition and a stated default for the conversion rate, so the schema carries the load. The description adds no extra meaning about input units or sensitivities beyond what the schema already says, which is the expected baseline.

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 opens with a specific verb (Calculate) and names concrete outputs — projected revenue growth, CAC reduction, and payback timeline — tied to a specific deployment of ADV Strategy Pro landing pages. That is far more informative than a restatement of the name, though it does not explicitly distinguish itself from the sibling knowledge/offer tools.

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 only implied: an agent can infer this is a what-if projection tool rather than a retrieval tool, and the sibling names suggest it is the only calculator here. There is no statement of prerequisites, when not to use it, or what to do with the resulting projection.

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