Skip to main content
Glama
Sign In

Asked Thrice

by com.askedthrice
OverviewDiscussionsAdmin

Start visibility check

start_visibility_check

Closed: Asked Thrice no longer runs free measurements. Calling it returns status closed and the link to the paid scan at askedthrice.com, which needs an account. Measurements started before the change can still be read with get_visibility_check.

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": {
      "brand": "<brand>",
      "website": "<website>",
      "category": "<category>"
    },
    "name": "start_visibility_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandYesBrand name as customers write it
websiteYesDomain, like yourbrand.com
categoryYesWhat the business sells, in plain words
languageNoLanguage the buyer questions are asked in
locationNoWhere the business competes, like 'Cordoba, Argentina'
competitorsNoUp to 5 real competitors, comma separated

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior1/5

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

The description says calling the tool returns status closed and a link, implying a read-like status response with no measurement creation, and that repeated calls behave the same. That contradicts readOnlyHint=false and idempotentHint=false, and the annotations conflict with the described behavior.

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?

The description is two tight sentences, front-loads the critical fact ('Closed'), and wastes no space. Every sentence adds useful information: closure, return behavior, paid alternative, and the read path for old measurements.

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

Completeness5/5

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

For a discontinued tool with no output schema, the description fully covers what a call now does, what it returns, and where to go instead. The full schema coverage handles parameter meaning, so no important context is missing beyond the annotation conflict scored separately.

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%, so the schema already documents brand, website, category, language, location, and competitors. The description adds no parameter-level meaning, which is acceptable at baseline 3 when the schema is rich, especially for a closed tool.

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?

The description states a specific resource and current behavior: the tool is 'Closed', no longer runs free measurements, and returns a closed status plus a paid-scan link. It clearly distinguishes itself from get_visibility_check, which is named for reading measurements started before the change.

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

Usage Guidelines5/5

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

It explicitly says the tool no longer runs free measurements, tells the agent what a call returns instead, and names get_visibility_check for pre-change measurements. The external paid scan at askedthrice.com needing an account is also a clear alternative flow.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Asked Thrice toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources