Skip to main content
Glama

MentionedOn Visibility and Website Fixes

Analyze AI Discovery Readiness

analyze_discovery_readiness
Read-only

Use when the user has no account: scores signals you collect yourself (schema present, name/address/phone consistency, profiles, reviews) for AI discovery readiness. Returns a score, the gaps in priority order and what still needs verifying. Free; it does not fetch the website, run a scan, store anything or confirm inclusion in any AI product.

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": {
      "businessName": "<businessName>",
      "signals": "<signals>"
    },
    "name": "analyze_discovery_readiness"
  }
}

Input Schema

NameRequiredDescriptionDefault
signalsYesCaller-supplied signal observations. Omitted signals are treated as unknown.
websiteUrlNoOptional page URL used only as a label. The tool will not fetch this URL.
businessNameYesThe business name used only to label this assessment.

Output Schema

NameRequiredDescriptionDefault
scopeYes
assessmentYes
prioritiesYes
scoreBasisYes
websiteUrlYes
limitationsYes
scoreStatusYes
businessNameYes
readinessScoreYesWeighted score over observed signals only. Null when no signal was observed or evidence coverage is below minimumCoveragePercent.
evaluatedSignalsYes
verificationNeededYes
minimumCoveragePercentYes
evidenceCoveragePercentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedOutput schema / properties / minimumCoveragePercent
      Added value: +{
      +  "maximum": 100,
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedOutput schema / properties / readinessScore / description
      Added value: +"Weighted score over observed signals only. Null when no signal was observed or evidence coverage is below minimumCoveragePercent."
    • addedOutput schema / properties / scoreBasis
      Added value: +{
      +  "const": "observed_signals_only",
      +  "type": "string"
      +}
    • addedOutput schema / properties / scoreStatus
      Added value: +{
      +  "enum": [
      +    "reported",
      +    "withheld_insufficient_coverage",
      +    "no_observed_signals"
      +  ],
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "scope",
      -  "businessName",
      -  "websiteUrl",
      -  "readinessScore",
      -  "assessment",
      -  "evidenceCoveragePercent",
      -  "evaluatedSignals",
      -  "priorities",
      -  "verificationNeeded",
      -  "limitations"
      -]New value: +[
      +  "scope",
      +  "businessName",
      +  "websiteUrl",
      +  "readinessScore",
      +  "scoreBasis",
      +  "scoreStatus",
      +  "minimumCoveragePercent",
      +  "assessment",
      +  "evidenceCoveragePercent",
      +  "evaluatedSignals",
      +  "priorities",
      +  "verificationNeeded",
      +  "limitations"
      +]
  2. First observed

TDQS

A4.4/5.0
Behavior4/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 the description's job is to add context — and it does: free of charge, no website fetch, no scan, no storage, and no confirmation of inclusion in any AI product. That preempts the most likely agent misconception (that this is a scan or a verification). It does not explain how unknown/omitted signals affect the score, which is the one behavioral gap.

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 sentences, front-loaded with the use condition, then the return shape, then the exclusions. Every clause carries distinct information — no restatement of the name or title.

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?

An output schema exists, yet the description still usefully summarizes the return ('a score, the gaps in priority order and what still needs verifying'). Combined with the no-fetch/no-store disclaimers, an agent has enough to invoke this correctly; only the treatment of 'unknown' versus 'missing' signals in scoring is left implicit.

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?

Schema coverage is 100%, so the baseline is 3; the description earns above that by characterizing the signal set the caller must supply ('schema present, name/address/phone consistency, profiles, reviews'), which tells an agent what evidence to gather before calling. It does not map its parenthetical examples onto the exact enum values, so it adds framing rather than new per-parameter detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('scores signals ... for AI discovery readiness') and immediately scopes it to caller-collected evidence rather than a fetched scan. The negative framing ('does not fetch the website, run a scan') separates it from inspection/scan siblings without needing their schemas.

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?

Gives an explicit triggering condition ('Use when the user has no account') and clear exclusions of what it will not do. It stops short of naming the alternative sibling to use when the user does have an account or a website, leaving the routing half-specified.

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