PreShiftIQ

My matches

my_matches

Read-onlyIdempotent

For the signed-in client (the evaluating company): the notified matches of the latest completed assessment, or of the assessment named by assessment_id, best score first, each as a masked card with its score and tier. On a review account the cards are its matches, and no vendor is contacted. A vendor's contact details appear only on a match that vendor has accepted, with the requirement and preference credits that vendor earned for you and the status of each certification you required; every other card stays masked. No card carries pricing.

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

Input Schema

Name	Required	Description	Default
`assessment_id`	No

Output Schema

Name	Required	Description	Default
`status`	Yes
`matches`	Yes
`summary`	Yes
`vertical`	Yes
`pending_delivery`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 7, 2026
- changedOutput schema / properties / matches / items / properties / vendor / properties / name / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

Changed1 schema field changedOct 17, 2026

changedOutput schema / properties / vertical / enum

Previous value: -[
-  "tms",
-  "dock-scheduling",
-  "eld",
-  "carrier-vetting",
-  "fleet-management",
-  null
-]New value: +[
+  "tms",
+  "dock-scheduling",
+  "eld",
+  "carrier-vetting",
+  "fleet-management",
+  "supply-chain-procurement",
+  "yard-management",
+  null
+]

Changed2 schema fields changedOct 17, 2026

removedOutput schema / properties / boundary_statement
```
Removed value: -{
-  "type": "string"
-}
```

changedOutput schema / required

Previous value: -[
-  "status",
-  "vertical",
-  "pending_delivery",
-  "matches",
-  "summary",
-  "boundary_statement"
-]New value: +[
+  "status",
+  "vertical",
+  "pending_delivery",
+  "matches",
+  "summary"
+]

Changed2 schema fields changedOct 10, 2026

addedOutput schema / properties / matches / items / properties / reversed
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / properties / matches / items / required

Previous value: -[
-  "match_id",
-  "masked_id",
-  "total_score",
-  "tier",
-  "accepted",
-  "vendor",
-  "credits"
-]New value: +[
+  "match_id",
+  "masked_id",
+  "total_score",
+  "tier",
+  "accepted",
+  "reversed",
+  "vendor",
+  "credits"
+]

Changed2 schema fields changedOct 7, 2026

addedOutput schema / properties / boundary_statement
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "status",
-  "vertical",
-  "pending_delivery",
-  "matches",
-  "summary"
-]New value: +[
+  "status",
+  "vertical",
+  "pending_delivery",
+  "matches",
+  "summary",
+  "boundary_statement"
+]

Changed2 schema fields changedOct 3, 2026

addedOutput schema / properties / matches / items / properties / credits

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "certifications": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "label": {
+            "type": "string"
+          },
+          "status": {
+            "enum": [
+              "met",
+              "unmet",
+              "not_assessed"
+            ],
+            "type": "string"
+          }
+        },
+        "required": [
+          "label",
+          "status"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "preference": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "requirement": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "requirement",
+    "preference",
+    "certifications"
+  ],
+  "type": [
+    "object",
+    "null"
+  ]
+}

changedOutput schema / properties / matches / items / required

Previous value: -[
-  "match_id",
-  "masked_id",
-  "total_score",
-  "tier",
-  "accepted",
-  "vendor"
-]New value: +[
+  "match_id",
+  "masked_id",
+  "total_score",
+  "tier",
+  "accepted",
+  "vendor",
+  "credits"
+]

Changed2 schema fields changedOct 2, 2026

addedOutput schema / properties / summary
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "status",
-  "vertical",
-  "pending_delivery",
-  "matches"
-]New value: +[
+  "status",
+  "vertical",
+  "pending_delivery",
+  "matches",
+  "summary"
+]

First observedOct 1, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the read-only and idempotent annotations, the description explains masking rules, review-account behavior, no vendor contact, when vendor contact details become visible, and that no card includes pricing. This is substantial behavioral disclosure that helps an agent understand exactly what the tool will and will not reveal.

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 core purpose and then adds only meaningful behavioral qualifications about review accounts, masking, accepted matches, and pricing. Despite being dense, every sentence contributes necessary context for a tool with nuanced visibility rules.

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?

Given that an output schema exists and annotations already state the safe read-only profile, the description provides enough context about matching, masking, vendor visibility, and assessment selection. Nothing critical for correct invocation appears to be missing.

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?

The schema description coverage is 0%, so the description must carry the meaning of assessment_id. It does so by explaining that the tool defaults to the latest completed assessment and can instead use the assessment named by assessment_id, though it does not state the UUID format or error behavior.

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 clearly identifies the resource and scope: notified matches for the signed-in evaluating company, either from the latest completed assessment or a named assessment. It also distinguishes the private, masked match view from a public catalog by stating that cards are masked and carry no pricing.

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?

It gives clear usage context: call this for the signed-in client's matches, and optionally target a specific assessment with assessment_id. It does not explicitly name when to use a different sibling tool or when not to use this one, so it falls short of full alternative 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.

My matches

Tool call template

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources