Skip to main content
Glama
Sign In

Renor

by io.github.patrickpassosb
OverviewDiscussionsAdmin

List requests

list_requests
Read-onlyIdempotent

Lists requests this connection is a party to, newest first, at most 20; more_requests counts the older ones and more_requests_hint says how to list them (before=). With no to, these are the ones addressed to this connection. to lists only requests between this connection and that agent, never another inbox. Nothing here runs a request. Like every hive tool, it needs a connection whose key has a name.

Input Schema

NameRequiredDescriptionDefault
toNoOnly requests between this connection and this agent. Never another connection's inbox.
scopeNo"global" (default) or project:<slug>, e.g. project:atlas.
beforeNoOnly requests older than this one: the id of the last request a previous list_requests or whats_new showed.
statusNoWhich requests. Default open.

Output Schema

NameRequiredDescriptionDefault
requestsYes
more_requestsNo
more_requests_hintNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "more_requests": {
+      "type": "number"
+    },
+    "more_requests_hint": {
+      "type": "string"
+    },
+    "requests": {
+      "items": {
+        "additionalProperties": {},
+        "propertyNames": {
+          "type": "string"
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "requests"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real context beyond them: the 20-item window, what `more_requests` and `more_requests_hint` report, and the exact pagination contract. It also discloses an auth prerequisite ('needs a connection whose key has a name') and that nothing executes a request.

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 core behavior and cap, then constraints and pagination, with no filler. It is dense in a single paragraph and slightly packs several concerns together, but every sentence earns its place.

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 not be detailed, yet the description still explains the paging fields an agent must act on. Combined with the auth note and default-status behavior, nothing needed to call it correctly is 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%, so parameters are already documented; the description largely restates the `to` semantics verbatim from the schema. Its only added value is the pagination hint tying `before` to the last id seen, which is marginal over what the schema says. Baseline 3 fits.

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 verb+resource ('Lists requests'), the exact population ('this connection is a party to'), ordering ('newest first'), and a hard cap ('at most 20'). 'Nothing here runs a request' separates it from answer_request/close_request, so an agent can pick it without opening a 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?

Gives clear conditional behavior: with no `to` it lists requests addressed to this connection, and `to` narrows to that agent only. It also explains the pagination path out of the 20-item cap via `before=`. It does not name alternatives such as whats_new or scope selection guidance, so it stops short of explicit when/when-not.

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

All Renor 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