Conecto

Make a PowerPoint deck

documents_create_deck

A PowerPoint deck from your slides, saved in the file store with a download link (and a PDF with pdf: true): title and section slides, bullet text, big-number KPIs, tables, native charts (bar, column, stacked, line, pie, radar) that stay editable, the football field from valuation_football_field (its deck_block), and images. Each slide can carry its sources, shown under it, and speaker notes. In Conecto's plain board style, or in the business's own template (a .pptx or .potx in the store): its layouts, fonts and colours. You write every word. Costs $0.10 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>",
      "slides": "<slides>"
    },
    "name": "documents_create_deck"
  }
}

Input Schema

Name	Required	Description
`pdf`	No
`name`	Yes	Name for the new file, e.g. "Quote 1042.pdf".
`accent`	No	The plain style's one colour, e.g. #1E3A8A.
`slides`	Yes
`link_hours`	No
`logo_file_id`	No	A PNG or JPEG logo for the title slide (plain style).
`template_file_id`	No	The business's own PowerPoint template; its sample slides are left out.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations supply the safety profile (readOnly false, destructive false, non-idempotent), and the description adds genuinely new behavioral context: the result is written to the file store with a download link, a PDF can be produced, and the call costs $0.10 with no charge on failure. Missing is anything on link expiry or limits (links expire per link_hours, max 40 slides), but the cost and output-location disclosure is valuable beyond annotations.

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?

Front-loads the outcome and then covers content types, styling, authorship, and cost in one dense but purposeful paragraph. Every clause adds information; the only cost is a slightly run-on reading experience from the long colon-delimited list.

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 complex tool with nested slide objects and no output schema, the description covers output destination (file store + link), PDF variant, styling modes, and the fact the agent must author all content. It leaves minor gaps on link lifetime and asset parameters, which the schema partially covers.

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 57%, so the schema carries much of the detail. The description adds meaning for pdf and the slide type taxonomy (which types take words vs figures vs images), but does not explain accent, link_hours, logo_file_id, decimals, or column_formats, leaving the agent to rely on the schema for those.

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 and resource ("A PowerPoint deck") and enumerates exactly what goes in (title/section slides, KPIs, tables, native charts, football field, images). This clearly separates it from documents_create_pdf and documents_convert_to_pdf, which handle non-deck output.

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?

Gives clear context for use: pdf: true for a PDF variant, a .pptx/.potx for template styling, and the deck_block hand-off from valuation_football_field. It never explicitly says when NOT to use it versus documents_create_pdf, but the deck-specific framing makes the boundary fairly obvious.

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?