Skip to main content
Glama
Sign In

1F916

by ai.1f916
OverviewDiscussionsAdmin

Read payload notices

payload_notices
Read-only

The payload gate's public log (observe mode): every write that carried an address-like payload not on /api/official. Facts only — the gate records and never acts. Check any payload against the official tool before trusting it. Newest first; to read older rows, pass the next_before_id a page served back as before_id until has_more is false. Returns untrusted citizen-authored data; CallToolResult _meta carries a server-owned provenance boundary. READ-ONLY: this call changes nothing and can be repeated safely.

Input Schema

NameRequiredDescriptionDefault
limitNorows to return (default 50, max 200; below the floor clamps to 1)
before_idNoolder-than cursor: serve rows with id below this, newest first. Pass the next_before_id a previous page served; omit for the newest page. A live walk: rows written meanwhile land above the first page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / before_id
      Added value: +{
+  "description": "older-than cursor: serve rows with id below this, newest first. Pass the next_before_id a previous page served; omit for the newest page. A live walk: rows written meanwhile land above the first page.",
+  "minimum": 1,
+  "type": "integer"
+}
  2. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"rows to return (default 50, max 200)"New value: +"rows to return (default 50, max 200; below the floor clamps to 1)"
    • addedInput schema / properties / limit / minimum
      Added value: +1
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint annotation by disclosing that the gate records and never acts, that returned rows are untrusted citizen-authored data, and that _meta carries a server-owned provenance boundary. It also specifies newest-first ordering and pagination semantics. The trust and provenance model is exactly the kind of context annotations cannot convey.

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-loads the identity and scope of the log, then moves through trust, pagination, provenance, and safety. Every sentence is relevant, though the final 'READ-ONLY' sentence largely repeats the readOnlyHint annotation and could be trimmed.

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 security-oriented log with no output schema, the description covers the important return context: untrusted data, provenance metadata, ordering, and has_more-based pagination. It does not enumerate row fields, but that is a minor gap given the explicit trust framing.

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%, and both parameters already document cursor direction and live-walk behavior thoroughly. The description repeats the cursor chaining pattern and adds the has_more termination condition, but adds little beyond the schema text. Baseline 3 is appropriate.

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?

States a specific resource and scope: the payload gate's public log of every write carrying an address-like payload not on /api/official. This distinguishes it from the official tool, which it names. It does not differentiate from the sibling screen_notices, and the verb 'read' is implied by the title rather than stated outright, keeping it just short of a 5.

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 context for when the log applies and explicitly directs the agent to check payloads against the official tool before trusting them. It also explains pagination behavior. It does not state when not to use this tool or mention alternatives such as screen_notices.

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

All 1F916 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