Skip to main content
Glama
Sign In

Conecto

by chat.conecto
OverviewDiscussionsAdmin

Set up AI visibility tracking

visibility_setup
Idempotent

Choose what to track for a website: the buyer questions to ask the assistants (up to 10), the competitors to compare against (up to 10, each with its domains), and which assistants to check (default: all of ChatGPT, Claude, Gemini, Grok, Perplexity, DeepSeek, AI Overviews). Send only what you want to change. Without questions, the first check writes five from the website. Costs $0.001 per call; nothing if it fails.

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": {
      "website": "<website>"
    },
    "name": "visibility_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
websiteYesThe business website, e.g. https://acme.com
questionsNo
assistantsNo
brand_nameNo
competitorsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Adds substantial behavioral detail beyond the annotations: exact cost ($0.001 per call, free on failure), default of all assistants, and the auto-generation of five questions when none are supplied. These are exactly the operational facts an agent needs that annotations don't carry.

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?

Dense but front-loaded: purpose first, then limits/defaults, then cost. Nearly every clause (cost, failure behavior, partial update) earns its place, though the long run-on sentence could be clearer.

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 mutation tool with no output schema and low schema coverage, it covers cost, defaults, partial-update semantics, and failure behavior well. The main omission is brand_name and question sub-field meaning, but overall it is sufficient to call the tool correctly.

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?

With only 20% schema coverage the description does heavy lifting—explaining questions (up to 10), competitors (up to 10, each with domains), and assistants (default all). But brand_name is completely unmentioned, and the topic/country sub-fields of questions are unexplained, leaving gaps.

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 action (configure what to track for a website) and enumerates the three configurable dimensions: questions, competitors, and assistants. Clear what the tool does, though it doesn't explicitly name a sibling alternative to distinguish the 'setup' step from visibility_check/report.

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?

'Send only what you want to change' clearly signals partial-update semantics, and 'without questions, the first check writes five from the website' explains a default path. However, it never states when to prefer this over siblings like visibility_check or visibility_improve, leaving the routing implicit.

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

All Conecto 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