Skip to main content
Glama
Sign In

SetLatch

by com.setlatch
OverviewDiscussionsAdmin

List privacy requests

list_requests
Read-onlyIdempotent

Privacy requests received by a site, newest first, each with requester, type, law, status and response deadline (all of them, no paging). Use it to find a request or see what is due; then get_request for one in full. Filter by status, or "open" for everything not yet completed or rejected.

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>"
    },
    "name": "list_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesThe site: its slug from list_sites (its id or exact name also work).
statusNoOnly requests in this status; "open" = not completed or rejected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: newest-first ordering, unpaged full result set, and the exact fields returned per request. It stops short of stating permissions or result-size expectations, so not quite 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?

Two sentences, front-loaded with the resource and scope, then routing guidance and filtering. Every clause carries information: ordering, completeness, returned fields, and the sibling alternative.

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?

With no output schema, the description compensates by enumerating the returned fields and confirming there is no paging. Combined with the explicit sibling routing and filter semantics, an agent has everything needed to call this correctly.

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 100%, so both parameters are already documented, including the 'open' enum meaning. The description restates the status filter and its 'open' shorthand but adds no syntax or format detail beyond the schema, which matches the baseline 3 for high-coverage schemas.

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 opens with a specific verb and resource ('Privacy requests received by a site') and immediately specifies scope (newest first, all of them, no paging) plus the returned fields. It also contrasts with the sibling get_request, so an agent can distinguish it without opening either schema.

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

Usage Guidelines5/5

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

It explicitly states when to use it ('find a request or see what is due'), names the alternative for detail ('then get_request for one in full'), and explains the status filter including the special 'open' value. Nothing about tool selection is left to inference.

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