Conecto

Set up the careers page

hiring_setup_careers

Idempotent

The careers page at cncto.co/j/ that lists the open jobs: its name, a short intro, the website, the address candidates' replies go to, and who hears about each application. Only what you pass changes. Costs $0.001 per call; nothing if it fails.

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": "hiring_setup_careers"
  }
}

Input Schema

Name	Required	Description
`name`	No
`intro`	No
`website`	No
`reply_to`	No
`ai_notice`	No	Your own words for that notice; "" for ours (a person decides, and how to ask a person to look again).
`ai_review`	No	Tell candidates on every application form that AI may help review applications, as the EU's AI Act asks. Required before screening with hiring_screen_queue.
`notify_email`	No
`application_limit`	No	At most count applications from one person in days, across every role, like {"count": 2, "days": 180}; the form says so. null: no limit.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare mutation, idempotency and non-destructiveness, so the description's main contributions are the cost model ('$0.001 per call; nothing if it fails') and the partial-update semantics, both useful and not in structured data. It still omits permission requirements and the fact that ai_review gates hiring_screen_queue, which is the one behavioral prerequisite an agent most needs.

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?

Two sentences, front-loaded with the resource and URL, then the field inventory, then the two operational facts. The field enumeration is a little list-like, but every clause carries information the agent needs.

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 non-destructive, idempotent settings-update tool with no output schema, the description covers location, scope, update semantics, and cost — close to enough to call it safely. It falls short on the compliance-related prerequisite (ai_review before screening) and on the format/limits of the passed fields.

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 only 38%, so the description should compensate more than it does. It does add meaning for 'name' by tying it to the URL path cncto.co/j/<name>, but for the other seven parameters it merely repeats field names (intro, website, reply_to, notify_email) without formats, constraints, or the unwritten implications of application_limit and ai_review.

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 concrete verb and resource ('careers page at cncto.co/j/<name>') and enumerates the field groups the page holds, so the agent knows exactly what is being configured. It does not distinguish itself from the nearby sibling hiring_design_careers, which a reader could easily confuse with this one.

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?

'Only what you pass changes' tells the agent this is a partial-update call, which is real usage guidance. However, there is no statement of when to use this versus hiring_design_careers, no prerequisites (e.g. that ai_review must be set before screening), and no mention of who may call it.

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?