Skip to main content
Glama

AI Visibility Audit

How to connect and what each server does

get_started
Read-onlyIdempotent

Explain what Tsoden SERP Checker can check without an account, what a connected account adds (tracked rankings and answer-engine visibility for the user's own projects) and how to connect it. Use it when the user asks how to connect an account or how to track results over time.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered structurally. The description adds genuinely useful context about the tool's content domain (free-tier capabilities vs. account-only features), which tells the agent what kind of answer to expect; it does not indicate the output form (text vs. structured), keeping it from 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?

Two sentences, both front-loaded and purposeful: the first defines the content, the second defines the trigger. No filler, no repetition of the title or annotations.

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-parameter informational tool with no output schema, the description covers what the answer will contain and when to call it. The only residual gap is the response format, which is minor for an explainer tool.

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 input schema takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies, and the definition correctly does not waste space restating an empty 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 gives a specific verb (explain) and a clearly scoped subject: what the checker can do without an account, what a connected account adds (tracked rankings, answer-engine visibility for the user's own projects), and how to connect. That is concrete enough to separate it from the audit/benchmark siblings, though it never names those siblings explicitly.

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 states the triggering conditions directly: use when the user asks how to connect an account or how to track results over time. There are no explicit when-not conditions or named alternatives, so it stops short of a full routing rule.

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