Skip to main content
Glama
Sign In

Conecto

by chat.conecto
OverviewDiscussionsAdmin

Start a checklist for someone

hr_start_checklist

Turn a checklist into tasks for one person, each due its due_days from their start date (onboarding) or last day (offboarding), which must be set. Refused while they still have open tasks from the same checklist. Returns the tasks with their task_id. 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": {
      "person": "<person>",
      "checklist": "<checklist>"
    },
    "name": "hr_start_checklist"
  }
}

Input Schema

NameRequiredDescriptionDefault
personYesThe person_id, or their work email.
checklistYesThe checklist's name.

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?

Beyond the annotations (which only say non-read-only, non-destructive, non-idempotent), the description discloses the refusal behavior, the required date fields, that tasks are created with due dates derived from due_days, the returned task_id values, and the $0.01 charge with no cost on failure. This is exactly the kind of behavioral context annotations cannot carry.

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?

Front-loads the core action, then preconditions, return value, and cost in quick succession. Every sentence (including the pricing note) carries actionable information with no filler.

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 two-parameter mutation with no output schema, the description covers preconditions, effects, return value (task ids), and billing. An agent has everything needed to decide and call correctly.

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 100%, so the parameters are already documented. The description adds operational meaning not in the schema: the person's start/last day drives due-date computation, and the checklist is referenced by name. It does not restate the email-or-id flexibility, but the added due-date logic is genuine value beyond the schema.

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?

Uses a specific verb ('Turn a checklist into tasks') with an explicit resource and scope ('for one person'). It clearly separates this from hr_save_checklist (which defines a checklist) by describing the materialization of tasks, so an agent can tell the two apart without opening schemas.

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 an explicit precondition and refusal condition: the person's start date (onboarding) or last day (offboarding) must be set, and the call is refused while they still have open tasks from the same checklist. It stops short of naming siblings like hr_save_checklist or hr_tasks as alternatives, so it is strong but not fully routing.

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