Conecto

Save a screening

hiring_record_screening

Save your review of one application: strong, partial or weak match, a short summary, and for each of the job's criteria whether the application shows it, with the words that show it. Its match score is the weighted share of the criteria it shows (unclear counts as not shown). When the job has a filter and the application passes it, the hiring team hears about it once, with your summary: by email and as the event hiring.candidate_passed. It moves nobody: decide with hiring_move_applicant. 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": {
      "applicant_id": "<applicant_id>",
      "match": "<match>",
      "summary": "<summary>"
    },
    "name": "hiring_record_screening"
  }
}

Input Schema

Name	Required	Description
`match`	Yes
`summary`	Yes
`criteria`	No	[{"id": "c1", "met": true\|false\|null, "evidence": "Led a team of four at ..."}]
`applicant_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 28, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations, it discloses the match-score calculation, the unclear-as-not-shown rule, the external notification side effect (email and hiring.candidate_passed event), non-movement of the applicant, and per-call pricing. These are exactly the behavioral details an agent needs before invoking a mutating, side-effecting tool.

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?

The description is front-loaded with the action and fields, then moves through scoring, notification behavior, non-movement, and cost. Every sentence adds distinct decision-relevant information with no 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?

For a four-parameter mutating tool with no output schema, the description covers the core scoring, side effects, pricing, and the key alternative. It omits whether repeated saves overwrite prior screenings and any permission requirements, which are relevant gaps given idempotentHint=false.

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 description coverage is only 25%, so the description must compensate. It explains the match enum values, the role of the summary, and the meaning of criteria as per-criterion evidence, including how unclear values affect the score; only applicant_id is left to the obvious parameter name.

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?

The description states a specific verb and resource: saving a review of one application with a match rating, summary, and criteria evidence. It explicitly distinguishes the tool from hiring_move_applicant, so an agent can tell whether it is saving a screening or changing applicant state.

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?

The description makes clear that this is for recording a completed review and explicitly says it does not move the applicant, directing the agent to hiring_move_applicant for that action. It also notes the notification condition, but it does not give broader when-to-use context such as when to screen versus when to fetch the queue.

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?