Skip to main content
Glama
Sign In

SetLatch

by com.setlatch
OverviewDiscussionsAdmin

Get a privacy request

get_request
Read-onlyIdempotent

One request in full (use list_requests to find its id): the requester, deadline, one task per data map system (with its connections, past look up and deletion runs in connected apps, the by-hand steps and what the requester will be told), uncoveredSources (data map systems with no task yet), correspondence, files and its audit trail.

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": {
      "site": "<site>",
      "request_id": "<request_id>"
    },
    "name": "get_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesThe site: its slug from list_sites (its id or exact name also work).
request_idYesThe request id: the full id from list_requests (a unique start of it also works).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds genuine context beyond that by enumerating the depth of the payload — per-system tasks with connections, past look-up and deletion runs, manual steps, uncoveredSources, correspondence, files and audit trail — warning the agent this is a heavy, deeply nested response with no output schema to reveal that.

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?

A single front-loaded sentence with the key fact ('One request in full') first and the prerequisite in parentheses. The trailing enumeration is long and comma-heavy but every element is substantive content about the payload.

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?

With no output schema, the description carries the burden of describing return contents and does so thoroughly, plus the input prerequisite. Read-only/idempotent semantics come from annotations, so nothing an agent needs to invoke this correctly appears to be missing.

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 coverage is 100%: the schema already explains that site accepts a slug/id/name and that request_id accepts a unique prefix. The description only reinforces where request_id comes from (list_requests), which is marginal added meaning over the schema; baseline 3 applies.

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 states the specific resource and scope ('One request in full') and explicitly separates it from the list tool. The verb is elliptical rather than explicit, but combined with the title an agent can tell exactly what is returned and how it differs from list_requests.

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 a clear prerequisite and routing hint: 'use list_requests to find its id', which tells the agent how to obtain the required request_id before calling. There is no explicit when-not-to-use case, but for a straightforward single-record fetch the context is adequate.

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

All SetLatch toolsInspect
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