PreShiftIQ

Vendor documents on my match

list_lead_documents

Read-onlyIdempotent

For the signed-in client: the documents a matched vendor has released to your company on one match, such as security documents, case studies, demo recordings and references. Each is listed with an in-app link. Where the vendor allows assistants to read an item, its content is included: a hosted link and its timestamped segments, or a reference's contact details. Files open only in PreShiftIQ. It also includes the vendor's security profile when the vendor has released it to you, with its answers where the vendor allows assistants to read it. Each read of an item's content or of the profile is recorded and shown to the vendor. Read only.

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": {
      "match_id": "<match_id>"
    },
    "name": "list_lead_documents"
  }
}

Input Schema

Name	Required	Description	Default
`match_id`	Yes

Output Schema

Name	Required	Description	Default
`items`	Yes
`status`	Yes
`summary`	Yes
`security_profile`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4/5.0

Behavior5/5

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

Goes well past the annotations: content is returned only where the vendor permits assistant reading, files open only inside PreShiftIQ, the security profile is included when released, and every read of content or profile is recorded and shown to the vendor. That audit-visibility disclosure is materially useful and non-obvious for a read-only call.

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 scope, then branched into content rules, file-open limitation, profile inclusion, and audit recording. Slightly dense with subordinate clauses, but each sentence conveys distinct behavior.

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 an output schema exists, the description need not explain return structure, yet it still characterizes what appears in results (links, timestamped segments, contact details, profile answers). Combined with the permission gating and read-recording disclosure, an agent has everything needed to call this correctly and understand consequences.

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?

The schema has one required parameter with 0% description coverage, so the description must carry it. 'On one match' conveys that match_id selects a single match, but it does not say where a match_id comes from (e.g., my_matches) or what an invalid one does.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

A specific verb-and-resource statement: documents a matched vendor has released to your company, scoped to one match, with concrete examples (security documents, case studies, demo recordings, references). It does not explicitly differentiate itself from siblings like fetch or my_matches, but no sibling is close enough to create ambiguity.

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

Usage Guidelines3/5

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

Establishes the audience and precondition ('For the signed-in client', 'on one match'), which implicitly tells the agent when this tool applies. It never states when not to use it, nor points to an alternative for obtaining a match_id or for documents on other matches.

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.