Skip to main content
Glama

RootMention SEO

calculate_seo_break_even

Read-only

Estimate incremental orders and visits needed to cover monthly SEO spend. A scenario calculation, not a forecast.

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": {
      "monthlySpend": "<monthlySpend>",
      "averageOrderValue": "<averageOrderValue>",
      "contributionMarginPercent": "<contributionMarginPercent>",
      "conversionRatePercent": "<conversionRatePercent>"
    },
    "name": "calculate_seo_break_even"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthlySpendYes
averageOrderValueYes
conversionRatePercentYes
contributionMarginPercentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety and side-effect questions are answered structurally. The description adds genuine interpretive context by framing the output as a deterministic scenario rather than a forecast. It stops short of disclosing assumptions the calculation makes (currency, whether spend is gross or net, how margin is applied), which matters for interpreting the result.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the purpose and followed by a single essential qualifier. Every clause earns its place and there is no boilerplate.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no description of what the response contains (e.g., required orders, required visits, implied revenue), so the agent must call blind. Combined with four required numeric parameters that have zero schema documentation, the definition is under-specified for a tool of this shape, even though its purpose is clear.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden of explaining the four required parameters, and it names none of them. Units are left ambiguous: monthlySpend has no stated currency, and conversionRatePercent/contributionMarginPercent have 0-100 bounds but the description never confirms they are whole percentages rather than fractions. This is a meaningful gap for a numeric calculator where a unit mistake silently produces wrong results.

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 output resource: 'Estimate incremental orders and visits needed to cover monthly SEO spend.' An agent knows exactly what the calculation produces. It does not name or contrast with any sibling, though the siblings listed (run_seo_audit, get_services) are clearly different activities, so the risk of confusion is low.

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?

'A scenario calculation, not a forecast' implies a planning/what-if context and warns against treating results as predictions, which is useful implied guidance. However, it never states when to reach for this tool versus the audit or services tools, nor any preconditions such as having spend and margin figures on hand.

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.