Skip to main content
Glama
Sign In
playcal

playcal

by RizgarOzan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

playcal_logs

Summarize a Unity log by collapsing repeated entries and showing the first real error or cause, with optional limits and a since-text filter.

Instructions

summarize a Unity log: collapse repeats, show the first cause

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": "playcal_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNolog file, or - for stdin (default: this machine's Unity Editor.log)
limitNomost distinct errors to list (default 20)
sinceNoonly read after the last line containing TEXT, e.g. "Reloading assemblies"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the burden, and it does disclose the key transformation (repeats collapsed, first cause surfaced). It leaves out whether the source file is modified (it is a read, but that is only inferable), the shape of the summary, and any size or performance limits on large logs.

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?

A single colon-structured sentence with the operation front-loaded and zero filler. It is efficient, though the extreme terseness means some behavioral context was simply omitted rather than compressed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (3 optional params, no nesting) and the schema is fully documented, so the basics are covered. With no output schema, the description should say more about what the summary contains (grouped errors, counts, cause chain), and it does not.

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 each parameter already has a clear description including the stdin/- convention and the `since` marker example. The description adds no parameter meaning beyond the schema, so the baseline 3 applies.

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 verb and resource ("summarize a Unity log") plus two concrete behaviors: collapsing repeats and surfacing the first cause. That distinguishes it reasonably from generic siblings like playcal_query or playcal_report, though it never names an alternative explicitly.

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?

Usage is only implied by the object being acted on: an agent can infer this is for triaging a Unity log rather than querying state. There is no explicit when-to-use, when-not-to-use, or pointer to a sibling such as playcal_query for broader log inspection.

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

Deploy Server

Other Tools