Conecto

Show someone a page of results

view_show

Draw numbers, charts, bars, tables, lists and text on one page and get a one-time link to it, to send to a person: the first browser that opens it keeps it for an hour, and an unopened link expires after 7 days. Conecto keeps no dashboards of its own; this is how a person sees what you found, from any area or anywhere else. blocks is a list, drawn top to bottom. Each block is one of: {"type": "heading", "text"}; {"type": "text", "text"} (blank lines make paragraphs); {"type": "metrics", "items": [{"label", "value", "format", "currency", "change" (percent), "better": "up"|"down", "note", "tone": "good"|"warn"|"bad"}]} (up to 8 numbers in a row); {"type": "chart", "title", "kind": "line"|"bar", "labels": [...], "series": [{"name", "values": [...]}], "format", "currency"} (up to 4 series of up to 400 points); {"type": "bars", "title", "label_header", "value_header", "items": [{"label", "value", "detail", "link", "country" (a two-letter code: shows the flag, and the name when label is left out)}], "format", "currency"} (ranked rows with a bar each, up to 50); {"type": "table", "title", "columns": [{"label", "format", "currency"}], "rows": [[...], ...]} (up to 12 columns and 500 rows); {"type": "list", "title", "items": [{"title", "text", "meta", "link"}]} (up to 100); {"type": "divider"}. format is number, percent (49 means 49%), currency (with currency, like "EUR"), seconds (a length of time), milliseconds or text. bars, table, list and metrics take "width": "half" to sit beside the next half block. 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": {
      "title": "<title>",
      "blocks": "<blocks>"
    },
    "name": "view_show"
  }
}

Input Schema

Name	Required	Description
`title`	Yes
`blocks`	Yes	blocks is a list, drawn top to bottom. Each block is one of: {"type": "heading", "text"}; {"type": "text", "text"} (blank lines make paragraphs); {"type": "metrics", "items": [{"label", "value", "format", "currency", "change" (percent), "better": "up"\|"down", "note", "tone": "good"\|"warn"\|"bad"}]} (up to 8 numbers in a row); {"type": "chart", "title", "kind": "line"\|"bar", "labels": [...], "series": [{"name", "values": [...]}], "format", "currency"} (up to 4 series of up to 400 points); {"type": "bars", "title", "label_header", "value_header", "items": [{"label", "value", "detail", "link", "country" (a two-letter code: shows the flag, and the name when label is left out)}], "format", "currency"} (ranked rows with a bar each, up to 50); {"type": "table", "title", "columns": [{"label", "format", "currency"}], "rows": [[...], ...]} (up to 12 columns and 500 rows); {"type": "list", "title", "items": [{"title", "text", "meta", "link"}]} (up to 100); {"type": "divider"}. format is number, percent (49 means 49%), currency (with currency, like "EUR"), seconds (a length of time), milliseconds or text. bars, table, list and metrics take "width": "half" to sit beside the next half block.
`subtitle`	No	A line under the title, like the period it covers.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A3.8/5.0

Behavior5/5

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

Goes well beyond annotations by disclosing the one-time link mechanics (first browser keeps it for an hour, unopened links expire after 7 days), the per-call cost ($0.01, free on failure), and that the tool creates a page rather than a persistent dashboard. These are exactly the behavioral details an agent needs before invoking a non-idempotent, non-read-only operation.

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?

Front-loads purpose and link behavior well, but then becomes a dense wall of block-type specifications that duplicate the schema. While the complexity justifies some length, the same information could be organized more scannably, and the duplication makes it longer than necessary.

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?

Covers the essentials for a complex, non-read-only tool with no output schema: what it creates, how the link behaves, cost, and block types. It could explicitly state the return value (the link itself) or error cases, but it is largely sufficient for correct invocation.

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 67%, so the schema already documents most parameters. The description’s lengthy block-format explanation is largely duplicated verbatim inside the schema’s blocks description, adding little semantic value beyond what the structured field already provides. Baseline 3 is appropriate.

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 verb and resource: drawing blocks on a page and getting a one-time link. The phrase 'this is how a person sees what you found' clarifies its role, but it never names or distinguishes from close siblings like view_save or view_link, so an agent must infer the boundary.

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

Usage Guidelines3/5

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

Implies usage ('to send to a person', 'from any area or anywhere else') but gives no explicit when-to-use or when-not instructions. No alternative tool is mentioned, so the agent must guess whether to use this or view_link/view_save for related tasks.

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

All Conecto tools Inspect

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

Need Help?