Skip to main content
Glama

AI Site Scorer

list_signals

List GEO signals from the evidence registry: what helps AI search engines find and cite a site, each with an evidence level (A = experiment/official, B = large correlation, C = practice, X = no effect) and sources. Free, no auth.

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

Input Schema

NameRequiredDescriptionDefault
axisNoFilter by axis.
levelNoFilter by evidence level.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses that the registry is free and requires no auth, and that each returned item carries an evidence level plus sources. It omits pagination behavior, result volume, and ordering, which keeps it short of a 5.

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?

One tight sentence front-loads the action and resource, then the level legend, then the access terms. Every clause conveys something an agent needs, with no filler.

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 zero-required-parameter list tool with no output schema, the description covers what the tool returns (signals with evidence level and sources), how to filter, and access conditions. Only pagination and result-size expectations are unaddressed, which is a minor gap.

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% with both enums documented, so the baseline is 3. The description adds genuine meaning by defining the level values (A = experiment/official, B = large correlation, C = practice, X = no effect), which the schema only labels as 'Filter by evidence level'; the axis enum remains unelaborated.

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?

States a specific verb and resource ('List GEO signals from the evidence registry') and explains what a signal is ('what helps AI search engines find and cite a site'). It does not explicitly distinguish itself from the sibling get_signal, though the list/get verb difference makes the split reasonably inferable.

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 implied by the framing — consult this registry to learn what helps AI search engines find and cite a site — and 'Free, no auth' tells the agent there is no cost barrier. There is no explicit when-not guidance or named alternative for retrieving a single signal.

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