Skip to main content
Glama

AI Site Scorer

get_visibility

Visibility tracking of a project in AI answers (citations, share of voice). Not available yet.

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_visibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose the single most important behavioral fact: the tool is not yet functional. Beyond that it says nothing about return shape, whether results are cached or time-scoped, or what happens with an omitted project_id.

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 compact sentences with no filler; the metric parenthetical is informative rather than padding. The main structural flaw is ordering — the availability warning should lead, since it changes whether an agent should read the rest at all.

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?

For a single-parameter tool with no annotations and no output schema, the description leaves the agent unable to predict any output or to resolve the optional project_id. Worse, the availability caveat is ambiguous — "not available yet" could mean unimplemented, gated, or returning empty results — so an agent cannot tell whether calling it is harmless or an error.

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?

The sole parameter, project_id, has 0% schema description coverage, and the description never explains it — notably not whether it is optional, what scope is used when it is omitted, or what format the identifier takes. With one undocumented parameter the description needs to compensate and does not.

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

Purpose3/5

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

"Visibility tracking of a project in AI answers (citations, share of voice)" identifies the resource and the metric family, but the operative verb is vague — "tracking" does not say whether this retrieves a stored snapshot, a time series, or a live computation. It also gives no hint of how it differs from siblings like get_report or get_signal, which sound equally like project-scoped retrievals.

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?

The one genuinely useful usage signal is "Not available yet," which tells an agent to avoid invoking it, but that information is buried at the end rather than stated up front. There is no positive when-to-use guidance and no named alternative for obtaining visibility/citation data.

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