Skip to main content
Glama
Sign In

Conecto

by chat.conecto
OverviewDiscussionsAdmin

Make the help center public

help_center_set_public
Idempotent

Open the published help center to everyone (or close it again). Opening it starts its rent, $5 a month from the balance; closing it stops the rent. Publishing the design is a separate step: help_center_publish. Costs $5 a month while the help center is public, $0.001 to close it ($5.00 a month while public; at most $5.00 a 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": {
      "public": "<public>"
    },
    "name": "help_center_set_public"
  }
}

Input Schema

NameRequiredDescriptionDefault
publicYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the billing consequence of the toggle: $5/month rent starts on open, stops on close, $0.001 to close, capped at $5.00 a call, and no charge on failure. That cost/irreversibility context is not derivable from idempotentHint/destructiveHint and is exactly what an agent needs before mutating billing state.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The cost model is stated twice: once as 'starts its rent, $5 a month from the balance' and again as the parenthetical '$5.00 a month while public; at most $5.00 a call'. Front-loading is good, but the duplicated and awkwardly parenthesized pricing could be one clean sentence.

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 one-boolean mutation with no output schema and clear annotations, the description covers effect, cost, and sibling disambiguation. What's missing is minor: whether a public URL becomes live, and whether publishing is a hard prerequisite.

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?

Schema coverage is 0% and the lone `public` boolean has no description, but the description supplies its meaning — true opens the center to everyone, false closes it again. Semantics are adequately compensated for a single-parameter 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?

States a specific verb+resource pair ('Open the published help center to everyone (or close it again)') and explicitly separates itself from the sibling that publishes the design, help_center_publish. An agent can distinguish this toggle from publish without opening either schema.

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?

Names the adjacent alternative (help_center_publish) and states that publishing the design is a separate step, which routes the agent correctly. It doesn't spell out prerequisites (e.g. that the help center likely needs to be published first) or say when not to use it, so it falls short of a full 5.

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