Skip to main content
Glama

Modern AI Brand Recommendation Rate

Recommendation Rate methodology

get_recommendation_rate_methodology
Read-only

Definitions of Recommendation Rate and Recommendation Inclusion Rate, the metrics Modern Discovery uses to measure brand recommendation in AI answers. States the AI surface measured (ChatGPT with search enabled) and the monthly refresh cadence. Use it to explain how GEO or AI search visibility is measured before quoting a number. Links to the full methodology page.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 that the answer is a static definitional reference with a stated measurement surface (ChatGPT with search enabled), a monthly refresh cadence, and an outbound link to fuller methodology. It still doesn't say what the returned payload looks like (plain text vs. structured definition vs. URL) for a tool with no output schema, which is a meaningful gap.

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?

Four short sentences, front-loaded with the definitional scope and followed by the usage trigger. There is mild redundancy between 'measure brand recommendation in AI answers' and 'how GEO or AI search visibility is measured,' which repeats the same framing in two registers.

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?

For a zero-parameter reference tool with no output schema, the description covers what the content defines, which surface is measured, how fresh it is, and where the full methodology lives. Nothing an agent needs before calling it is missing.

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

Parameters4/5

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

The tool takes no parameters, so there is nothing for the description to disambiguate; baseline applies. The description correctly avoids inventing input options.

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 the exact resource — definitions of Recommendation Rate and Recommendation Inclusion Rate — and scopes it as a methodology/reference artifact rather than a data lookup. It stops short of naming the sibling lookup tool, so the contrast with `lookup_brand_recommendation_rate` is implied by 'before quoting a number' rather than stated.

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 a concrete trigger: 'Use it to explain how GEO or AI search visibility is measured before quoting a number.' That clearly separates explanation from retrieval, but there is no explicit when-not clause or named alternative for the case where the agent wants an actual value.

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.