PreShiftIQ

Ask to submit my assessment

request_assessment_submit

Destructive

For the signed-in client (the evaluating company): asks to submit a completed assessment for matching. Nothing is submitted by this tool: it returns a link to PreShiftIQ's own confirm page, where the person signed in to this account confirms. Where the assistant supports it, the link opens as a confirmation request. The link works for 30 minutes.

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": {
      "assessment_id": "<assessment_id>"
    },
    "name": "request_assessment_submit"
  }
}

Input Schema

Name	Required	Description	Default
`assessment_id`	Yes

Output Schema

Name	Required	Description	Default
`errors`	No
`status`	Yes
`summary`	Yes
`expires_at`	Yes
`confirm_url`	Yes
`proposals_recorded`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations only flag destructiveHint=true and idempotentHint=false; the description adds the crucial context that this tool itself submits nothing, returns a link to an external confirm page, may surface as a confirmation request, and that the link expires in 30 minutes. That explains why a destructive-hinted tool performs no direct mutation, which is exactly the kind of context annotations cannot convey.

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?

Four short sentences, front-loaded with the actor and action, then the non-submission caveat and link behavior. Every sentence carries information, though the confirmation-request sentence is slightly tangential.

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

Completeness5/5

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

For a one-parameter tool with an output schema, the description covers the actor, the two-step confirmation flow, and link lifetime. The only omission is parameter meaning, which is scored separately.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single parameter assessment_id is never mentioned in the description, so an agent gets no guidance on what identifier is expected (e.g. whether it must be the caller's own assessment). The description does not compensate for the schema gap.

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 ('asks to submit a completed assessment for matching') and immediately scopes it to the signed-in evaluating company, which separates it from siblings like start_assessment and submit_proposal_package. An agent can tell what this does without opening the schema.

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 this is the step for a completed assessment belonging to the signed-in client, and that confirmation happens elsewhere. It does not explicitly name an alternative tool or state when-not to use it, so it falls short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All PreShiftIQ 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.