Skip to main content
Glama
Sign In

Conecto

by chat.conecto
OverviewDiscussionsAdmin

Applications to screen

hiring_screen_queue
Read-onlyIdempotent

The next applications nobody has screened yet, oldest first, with what a review needs: the job, its criteria and filter, the answers and flags, the cover letter and the résumé as text. Blind by default: name, email, phone and links are left out and replaced in the text, so the review rests on what they did. Review each one yourself and save it with hiring_record_screening; Conecto never rejects anyone. To screen each application as it arrives, send hiring.application_received to your webhook with notify_subscribe, or read account_events. 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": "hiring_screen_queue"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobNoThe job (its slug from hiring_list_jobs).
blindNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover the read-only/idempotent safety profile, but the description adds genuinely non-obvious behavior: blind mode is on by default and names, emails, phones and links are redacted inside the text, and Conecto never auto-rejects applicants. The 'Free' note is an extra operational detail beyond structured fields.

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 what the tool returns and then the blind/save guidance, with every clause carrying information. It runs long as a single unbroken block, which slightly hurts scannability, but no sentence is filler.

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?

With no output schema, the description usefully enumerates the returned fields (job, criteria, filter, answers, flags, cover letter, résumé text), which is the critical missing piece. The only real gap is the undocumented `limit` batching behavior.

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 33%, so the description must carry more weight. It explains blind-mode semantics and the oldest-first ordering in prose, but never mentions the `limit` parameter (default 5, max 10), leaving the agent to discover the batching constraint from the schema alone.

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 ('the next applications nobody has screened yet, oldest first') and enumerates the payload contents an agent will get back. It is clearly distinguishable from hiring_list_applicants and hiring_get_applicant by its 'not yet screened' scoping.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit next step ('save it with hiring_record_screening') and names a concrete alternative pathway for a different need ('to screen each application as it arrives, send hiring.application_received ... or read account_events'). The when-to-use-this vs. when-to-use-something-else boundary is fully spelled out.

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