Skip to main content
Glama
Sign In

Conecto

by chat.conecto
OverviewDiscussionsAdmin

Create a website

website_create

Start a website for the business at cncto.co/w/: a draft with a home page, drawn in the brand kit (account_set_brand: logo and colour). Build it with website_save_page, look at it with website_preview, put it online with website_publish. Nothing is public and nothing is charged by the month until it is published. Costs $0.01 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": {
      "name": "<name>",
      "title": "<title>"
    },
    "name": "website_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesLowercase letters, digits and dashes, e.g. "halverson-cycle".
titleYesThe site's name, shown in the header and in titles.
languageNoe.g. "en", "de", "pt-BR". Default "en".
descriptionNoOne or two sentences for search engines and link previews.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare it is a non-destructive, non-idempotent write; the description adds substantial context beyond that: creation is draft-only, nothing is public or billed monthly until published, each call costs $0.01, and failures are free. Pricing and visibility state are exactly the traits an agent needs before invoking.

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?

Four short sentences, front-loaded with the action and URL, then the workflow, then billing/visibility terms. Every sentence contributes distinct information with no repetition.

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 create tool with no output schema, the description covers what is created, how to continue the workflow, visibility state, and cost. Nothing an agent needs in order to call it correctly is missing.

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% and documents all four parameters with formats, so the schema does the heavy lifting. The description only lightly adds meaning by showing <name> as the URL path segment (cncto.co/w/<name>); title, language and description are not discussed beyond the schema. Baseline 3 is appropriate.

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?

Specific verb+resource ('Start a website for the business') plus concrete output details: a draft with a home page rendered in the brand kit, at a named URL pattern. It also distinguishes itself from the surrounding website_* tools by describing the build/preview/publish workflow.

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?

Explicitly routes the agent to the correct siblings: build with website_save_page, inspect with website_preview, go live with website_publish. The order and condition for each step is stated, leaving nothing to inference.

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