Conecto

List checklist tasks

hr_tasks

Read-onlyIdempotent

Checklist tasks, soonest due first: open (default), overdue, done or all; for one person, one owner (person, manager, hr, it), or due on or before a date. Each names who does it: the person or their manager, with their work email. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "hr_tasks"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`owner`	No
`offset`	No
`person`	No	The person_id, or their work email.
`status`	No		open
`due_before`	No	Only tasks due on or before this date.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With read-only, idempotent, and non-destructive annotations already covering safety, the description adds valuable behavior: ordering ('soonest due first'), default status, and what each task includes ('who does it... with their work email'). It does not mention pagination behavior, but the annotations and schema reduce the burden.

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?

The description is compact and front-loads the core resource, ordering, and filters. The final word 'Free.' is terse and slightly ambiguous, but overall it is efficient with little wasted text.

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 six-parameter read-only listing tool with no output schema, the description covers ordering, default status, filters, and key return contents. It omits pagination details and full task field descriptions, so it is strong but not exhaustive.

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 description coverage is low at 33%, and the description compensates for several functional parameters: status values with default, owner options, person eligibility, and due-date semantics. However, it says nothing about limit or offset, leaving pagination behavior undocumented.

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?

The title 'List checklist tasks' and the description clearly identify an HR checklist-task listing tool, with status, owner/person, and due-date filters. It distinguishes itself from completion/start siblings by being a read-only list, but it does not explicitly contrast itself with related list tools such as tasks_list or crm_list_tasks.

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?

The description gives useful filtering context and states the default status ('open'), but it does not say when to use this tool versus sibling list tools or when not to use it. Usage is implied by the filter values rather than explicitly guided.

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?