Skip to main content
Glama

Can Beacon serve this site

check_coverage

Whether Beacon can score a website and install on it, from the published platform list and Beacon's address rules. Nothing is fetched in this call: what can only be known from the site itself is answered "we will check it when we score it".

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": {
      "site": "<site>"
    },
    "name": "check_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesthe website, e.g. example.com
platformNowhat it is built on, if known, e.g. WordPress

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?

With no annotations, the description does real work by disclosing that 'nothing is fetched in this call' and that the answer derives only from a published platform list plus address rules. It also warns that site-specific facts return a sentinel 'we will check it when we score it', which is valuable. It says nothing about permissions, cost, or how definitive a positive/negative answer is at the margins.

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?

Two sentences, both load-bearing: the first defines the answer's basis, the second defines what it cannot know. Slightly compressed phrasing ('install on it') costs a little clarity but nothing is padding.

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

Completeness3/5

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

For a two-parameter, read-only existence check with no output schema, the description never says what a result looks like — boolean plus reason, a coverage verdict, or a list of matches. Quoting the deferred-answer string hints at the shape but leaves a real gap an agent needs to plan a call.

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 100% with clear per-field descriptions for 'site' and 'platform', so baseline is 3. The description adds only indirect meaning (the platform list is 'published', platform input is optional) and no syntax or format guidance 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?

The description states the concrete question answered: whether Beacon can 'score a website and install on it', scoped to the 'published platform list and Beacon's address rules'. That is specific enough to distinguish it from an action tool, though the phrasing 'can score ... and install' briefly risks reading as if the tool itself installs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to call this versus not calling it, nor any prerequisite or follow-up step (e.g. call before create_order style flows). The only implicit guidance is that it is a pre-check whose answers may be deferred to scoring time, which an agent must infer.

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