PreShiftIQ

My clients

my_clients

Read-onlyIdempotent

For a signed-in consultant or private equity firm member: the assessments of the clients the firm represents (the companies evaluating technology) who have accepted the advisor disclosure, in any status, each with its status, its Tier 1 and Tier 2 completion percentages, the number of its matches awaiting release to vendors and, once matches exist, its notified match cards masked exactly as the client sees them. A represented client who has not accepted the disclosure is only counted, as withheld. Available once the consultant disclosure is open.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	Yes
`summary`	Yes
`represented`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026

changedOutput schema / properties / represented / items / properties / buyers / items / properties / vertical / enum

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

Changed2 schema fields changedOct 17, 2026

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

changedOutput schema / required

Previous value: -[
-  "status",
-  "represented",
-  "summary",
-  "boundary_statement"
-]New value: +[
+  "status",
+  "represented",
+  "summary"
+]

Changed1 schema field changedOct 16, 2026

changedOutput schema / properties / status / enum

Previous value: -[
-  "represented",
-  "no_account",
-  "no_firm"
-]New value: +[
+  "represented",
+  "no_account",
+  "no_firm",
+  "two_factor_required"
+]

Changed2 schema fields changedOct 10, 2026
- addedOutput schema / properties / represented / items / properties / buyers / items / properties / matches / items / properties / reversed
```
Added value: +{
+  "type": "boolean"
+}
```
- changedOutput schema / properties / represented / items / properties / buyers / items / 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",
-  "represented",
-  "summary"
-]New value: +[
+  "status",
+  "represented",
+  "summary",
+  "boundary_statement"
+]

Changed2 schema fields changedOct 6, 2026

addedOutput schema / properties / represented / items / properties / buyers / items / properties / pending_delivery
```
Added value: +{
+  "type": "integer"
+}
```

changedOutput schema / properties / represented / items / properties / buyers / items / required

Previous value: -[
-  "assessment_id",
-  "vertical",
-  "status",
-  "submitted_at",
-  "tier1_completion_pct",
-  "tier2_completion_pct",
-  "matches"
-]New value: +[
+  "assessment_id",
+  "vertical",
+  "status",
+  "submitted_at",
+  "tier1_completion_pct",
+  "tier2_completion_pct",
+  "matches",
+  "pending_delivery"
+]

Changed3 schema fields changedOct 6, 2026
- addedOutput schema / properties / represented / items / properties / buyers / items / properties / tier1_completion_pct
```
Added value: +{
+  "type": "integer"
+}
```
- addedOutput schema / properties / represented / items / properties / buyers / items / properties / tier2_completion_pct
```
Added value: +{
+  "type": "integer"
+}
```
- changedOutput schema / properties / represented / items / properties / buyers / items / required
```
Previous value: -[
-  "assessment_id",
-  "vertical",
-  "status",
-  "submitted_at",
-  "matches"
-]New value: +[
+  "assessment_id",
+  "vertical",
+  "status",
+  "submitted_at",
+  "tier1_completion_pct",
+  "tier2_completion_pct",
+  "matches"
+]
```
AddedOct 5, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds meaningful behavioral context beyond that: the caller must be an authenticated advisor, a disclosure must be accepted or the client is only counted as 'withheld', and match cards are masked exactly as the client sees them.

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-loaded with the required caller identity and scoped tightly to the subject matter, with no filler. It is a single dense, heavily-nested sentence, so the edge-case clauses (withheld clients, masking) are harder to scan than a short bulleted form would be.

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?

An output schema exists, so return values need no further explanation, and the description still covers access requirements, entry contents, the withheld-client edge case and the mask-once-matches-exist condition. Nothing an agent needs to call this zero-parameter read tool correctly is 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?

Zero parameters, so the baseline of 4 applies; there is nothing for the description to clarify, and it correctly spends no words on parameter syntax.

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 resource (the assessments of clients the firm represents) with named scope (signed-in consultant or PE firm member) and enumerates exactly what each entry contains (status, Tier 1/2 completion, matches awaiting release, masked match cards). An agent can distinguish this from my_assessment_status and my_matches without opening any 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?

Clear audience gating ('For a signed-in consultant or private equity firm member') and a precondition ('Available once the consultant disclosure is open') tell the agent when this tool is callable. It does not name a sibling as an alternative, so the routing against other 'my_*' tools is left implicit.

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.

Resources

Need Help?