Skip to main content
Glama
Sign In
playcal

playcal

by RizgarOzan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

playcal_ingest

Validate gameplay events from JSONL files or pasted PC0 blobs against the event schema, and route valid events and rejected lines with reasons.

Instructions

validate gameplay events (JSONL or pasted PC0 blobs) against the event schema

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": {
      "files": "<files>"
    },
    "name": "playcal_ingest"
  }
}

Input Schema

NameRequiredDescriptionDefault
outNowhere valid events go (default: accepted.jsonl)accepted.jsonl
filesYesJSONL files, or '-' for stdin
pasteNoinputs are free text containing PC0: blobs
rejectedNowhere invalid lines go, with a reasonrejected.jsonl

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, yet it only says "validate", which reads as a passive check while the tool actually writes accepted and rejected JSONL files. It does not disclose write side effects, exit behavior on failure, whether validation is schema-versioned, or what happens to stdin input. The output-file behavior is documented only in the schema, not the description.

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 front-loaded clause with the verb first and no wasted words. Its terseness is a completeness problem rather than a conciseness problem, so it stays high here.

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?

For a moderate-complexity tool with four fully documented parameters and no output schema, the description is minimally adequate: an agent can figure out the format combination. It omits side effects, error/exit semantics, and how validation failures are surfaced beyond the rejected file, leaving real gaps.

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%, so all four parameters, including defaults for out and rejected, are already documented. The description only adds that input may be JSONL or pasted PC0 blobs, which loosely maps to the files and paste parameters, so 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?

Names a specific action ("validate") and resource ("gameplay events"), and adds the accepted input formats (JSONL, pasted PC0 blobs), which is more than a name restatement. It does not explicitly separate itself from siblings like playcal_query or playcal_checkpoint, so it stops short of 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 implies a pipeline position (validate events before they are ingested elsewhere), but gives no when-to-use/when-not guidance, no prerequisites, and names no alternative sibling. Usage is inferable only from the verb and formats rather than stated.

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