PreShiftIQ

Read one PreShiftIQ document

fetch

Read-onlyIdempotent

Returns one published PreShiftIQ document by its id: its title, its text and its URL.

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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes

Output Schema

Name	Required	Description	Default
`id`	Yes
`url`	Yes
`text`	Yes
`title`	Yes
`metadata`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 17, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The rich annotations (readOnly, idempotent, non-destructive, closed-world) already cover the safety profile, so the bar is lower. The description still adds real behavioral context by restricting scope to 'published' documents and stating the payload contents (title, text, URL). It omits error behavior for missing or unpublished ids, which keeps it from a 5.

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?

One sentence, front-loaded with the verb and resource, with the returned fields listed last where they belong. Nothing redundant or padded.

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 single-parameter read tool with a full set of annotations and an output schema (so return values need not be re-explained), this is close to sufficient. The remaining gap is how failures for unknown or unpublished ids surface, plus where the id is expected to come from.

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?

Schema description coverage is 0%, but the single 'id' parameter is constrained by a regex pattern and length bounds, so format is largely defined structurally. The description adds only that the id identifies a document (not, say, a workspace), which is marginal added meaning over the schema.

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?

The description uses a specific verb ('Returns') and a precisely scoped resource ('one published PreShiftIQ document by its id'), and enumerates the returned fields. It clearly differs from the sibling 'search' tool, but it never names that sibling to make the contrast explicit.

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?

Usage is only implied: 'by its id' suggests a follow-up to a search or listing call, and 'published' implies unpublished documents are unreachable. There is no explicit when-to-use statement, no mention of the 'search' sibling, and no guidance on what to do when the id is unknown.

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.