Soleil Clusters

Audit log

list_audit

Read-onlyIdempotent

Recent API writes and image-byte fetches: who, what, when, with which token. Covers this account and, for a workspace owner, its service accounts; not edits made in the app.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_audit"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Default 100, max 500
`since`	No	ISO timestamp
`cursor`	No	next_cursor from the answer before

Output Schema

Name	Required	Description	Default
`entries`	No
`has_more`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the description is free to add the genuinely new facts: the exact event classes captured, that access extends to service accounts for workspace owners, and that in-app edits are silently absent. That last omission is a real behavioral caveat an agent needs. It says nothing about retention window or ordering, but the output schema covers the payload.

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 front-loaded sentence with a colon-enumerated payload summary followed by a scope sentence; every clause carries information and nothing is repeated from annotations or schema.

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 a rich output schema, full parameter documentation and safety annotations, the description only needs to supply event coverage and scope, which it does. A note on how far back 'recent' reaches would close the last gap an agent might care about.

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% (limit default/max, since as ISO timestamp, cursor as next_cursor), so the schema already carries the parameter meaning. The description adds no filtering or pagination guidance beyond it, which is the baseline for full coverage.

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 (recent API writes and image-byte fetches) and enumerates the record fields the agent will get back (who, what, when, token). It also scopes the tool explicitly to this account plus service accounts for workspace owners, which no sibling (whoami, search, fetch) claims.

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 a clear inclusion boundary (API writes and image-byte fetches) and an explicit exclusion (app edits are not covered), plus the account/workspace-owner scope condition. It does not name a competing sibling tool to prefer for the other cases, so it stops short of full when/when-not routing.

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

All Soleil Clusters 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.