Roundtable

Get Logs

get-logs

Read-onlyIdempotent

Query structured logs from your MCP tool executions. Filter by session, severity level, event type, and time range. Useful for debugging and monitoring tool usage.

Input Schema

TableJSON Schema

Name	Required	Description
`event`	No	Filter by event name (e.g., "debate_completed")
`level`	No	Filter by log level
`limit`	No	Max results
`offset`	No	Pagination offset
`end_time`	No	End timestamp (ms) for time range filter
`session_id`	No	Filter logs for a specific session
`start_time`	No	Start timestamp (ms) for time range filter

Output Schema

TableJSON Schema

Name	Required	Description	Default
`logs`	Yes	Matching log entries

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedMar 26, 2026

changedOutput schema / properties / logs / items / properties / data / anyOf

Previous value: -[
-  {
-    "additionalProperties": {},
-    "propertyNames": {
-      "type": "string"
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "number"
+        },
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "propertyNames": {
+      "type": "string"
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

First observedMar 11, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds little behavioral context beyond the resource type and filters; it does not mention pagination behavior, ordering, or other operational details. With annotations covering safety, a 3 is appropriate.

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?

The description is two sentences, front-loaded with the primary action and resource, and follows with a compact list of filters and a use case. Every sentence serves a purpose with 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?

For a read-only log query tool with a rich schema, output schema, and annotations, the description adequately covers the resource, filters, and use case. It does not explain return values (handled by output schema) and does not need to describe every filter detail since the schema does.

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 the schema fully documents all 7 parameters. The description mentions 'session, severity level, event type, and time range,' which maps to session_id, level, event, and start/end_time, but this adds minimal value beyond the schema's own descriptions.

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?

The description uses a specific verb ('Query') and resource ('structured logs from your MCP tool executions'), which is clear and distinguishes it from generic logging tools. However, it does not explicitly differentiate from sibling tools like 'debug-issue' or 'get-session', so it falls 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 Guidelines3/5

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

The description provides an implied use case ('Useful for debugging and monitoring tool usage') but does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. This is minimal guidance, landing at a 3.

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

All Roundtable tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation4/5

The tool set separates general consultation (consult-council) from specialized councils for tradeoffs, debugging, architecture, implementation planning, and code review. Session management and utility tools (logs, usage, models, sessions) are clearly distinct. Only minor potential overlap exists between consult-council and the specialized councils, but descriptions clarify the purpose of each.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case (e.g., consult-council, get-session, list-models). Verbs are varied but predictable, and compound nouns are hyphenated consistently. No mixed conventions.

Tool Count5/5

13 tools is appropriate for a platform that offers multiple council workflows plus session, log, and usage management. Each tool addresses a distinct need without unnecessary bloat.

Completeness5/5

The server covers the full lifecycle of a council-based workflow: model discovery (list-models), execution (consult-council and specialized councils), session retrieval (list-sessions, get-session), sharing (get-thread-link, set-thread-visibility), and operational support (check-usage, get-logs). Missing delete/update session tools are minor and not essential for the core purpose.

Resources

Need Help?