Conecto

List people

hr_list_people

Read-onlyIdempotent

People on the account by last name; by default everyone who hasn't left (current, future joiners included). Filter by status (active, on_leave, left, all), department, location, manager (their direct reports), employment type, or search words across names, emails and job title (every word must match). 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_list_people"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`offset`	No
`search`	No
`status`	No		current
`manager`	No	The person_id, or their work email.
`location`	No
`department`	No
`employment_type`	No

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?

Annotations already cover safety (readOnly, idempotent, non-destructive), so the bar is lower. The description adds real behavioral nuance: default inclusion of future joiners, exclusion of people who left, sorting by last name, and 'Free' (no credit cost).

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?

One dense but readable sentence with the default scope front-loaded and filters enumerated afterward. Every clause earns its place, though the semicolon-chained structure is slightly heavy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and a read-only list tool, the description is mostly complete on filters and defaults. However, it does not mention pagination (limit default 100, max 500, offset) or anything about the shape of returned records, leaving an agent to infer call batching.

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 only 13%, so the description must compensate, and it largely does: it explains status semantics beyond the enum, defines manager as direct reports, clarifies search covers names/emails/job title with AND matching, and covers department, location, and employment type. It omits limit/offset pagination meaning.

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+resource ('People on the account by last name') and clarifies the default scope (everyone who hasn't left, including future joiners). It does not explicitly differentiate from siblings like hr_get_person or admin_list_people, but the listing semantics are clear.

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 implies usage for roster lookups and enumerates filters, but gives no explicit when-to-use vs when-not or alternative tool routing (e.g., use hr_get_person for a single person). Usage context is present but alternatives are not.

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?