turnale

Get change log

get_audit_log

Read-only

Chronological record of every change (newest first) — the answer to "who changed that?". Paginate with before_id. Ids are global across all tournaments, so gaps between ids are normal.

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": {
      "tournament_key": "<tournament_key>"
    },
    "name": "get_audit_log"
  }
}

Input Schema

Name	Required	Description
`limit`	No
`before_id`	No
`tournament_key`	Yes	The tournament's organiser key (starts with tk_)

Output Schema

Name	Required	Description	Default
`entries`	Yes
`next_before_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 1, 2026
- removedOutput schema / properties / next_before_id / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / next_before_id / type
```
Added value: +[
+  "number",
+  "null"
+]
```

Changed2 schema fields changedAug 12, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

First observedJul 29, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly/non-destructive/non-open-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: newest-first ordering, cursor pagination via before_id, and the crucial note that ids are global so gaps between ids are normal — preventing a false 'entries were deleted' inference.

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?

Three short clauses: what it is, how to paginate, and the id-gap caveat. Front-loaded with the resource and ordering, no filler.

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?

An output schema exists, so return shape need not be explained, and the description covers ordering, pagination, and the id-gap pitfall. The remaining hole is limit behavior (default/max semantics), which is undocumented in both schema and description.

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 only 33% (only tournament_key is documented, as starting with tk_). The description adds meaning for before_id as a pagination cursor, but says nothing about limit (max 200, default value) or whether before_id is exclusive or inclusive. Useful but not compensatory for the coverage gap.

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 the specific resource (chronological record of every change), the ordering (newest first), and frames the use case ('who changed that?'). This clearly separates it from mutating siblings like undo_last_change or record_results, which alter state rather than report it.

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

Usage Guidelines3/5

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

The description implies the use case (attribution / history lookup) and notes pagination with before_id, but never states when to pick this over siblings such as get_briefing or undo_last_change, nor any exclusions. Usage is inferable but not spelled out.

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

All turnale 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.