Skip to main content
Glama
Sign In

Kineticist

by com.kineticist
OverviewDiscussionsAdmin

What's new in pinball

whats_new
Read-onlyIdempotent

What's new in pinball: "what's new in pinball this week?", "latest pinball news", "what's climbing the Hype Index?". The latest Kineticist news articles (headline, date, summary and link; members_section means part of the article is for members; games lists the machines an article covers, get_game_details with a game's slug returns its editions, prices and design team; a release announced in the last few days may not have its new editions in the database yet, so check the edition dates against the article before quoting prices), new videos, podcasts and posts from the pinball creators Kineticist follows (from_creators: title, creator, format, date, summary, link), and Kineticist's Hype Index ranking (the current top 10 and this week's biggest climbers; change_this_week and up are places moved on the index since a week ago, positive is up, and a missing change means there's no rank from a week ago). This covers the week in pinball; each article and creator item carries its link.

Input Schema

NameRequiredDescriptionDefault
daysNoHow far back to look for news, in days (default 7)
creatorsNoHow many creator items to list (default 8). Ask for more, up to 40, for a full roundup of the window

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / creators
      Added value: +{
+  "description": "How many creator items to list (default 8). Ask for more, up to 40, for a full roundup of the window",
+  "maximum": 40,
+  "minimum": 1,
+  "type": "integer"
+}
  2. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, the description explains field semantics such as `members_section`, `games`, `from_creators`, `change_this_week`, `up`, and a data-freshness caveat about recently announced editions not yet in the database. That is substantial behavioral context that an agent cannot infer from annotations alone.

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?

The description is front-loaded with the purpose and example queries, and it has enough detail for a rich aggregate tool. However, it is a single dense paragraph with nested parentheticals, which makes it slightly harder to scan than a cleaner structured layout would be.

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

Completeness5/5

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

Given the lack of an output schema and the aggregated nature of the tool, the description does a thorough job of explaining the returned sections, field meanings, and a subtle data-freshness caveat. Combined with the annotations and fully described parameters, an agent has everything needed to invoke it correctly.

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 both parameters are already documented in the input schema. The description implies the default week window but does not add syntax, limits or guidance for `days` or `creators` beyond what the schema provides, so the baseline 3 is appropriate.

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?

The description opens with a specific purpose and concrete example queries, then enumerates exactly what the tool returns: Kineticist news articles, creator videos/podcasts/posts, and the Hype Index. It also distinguishes itself from get_game_details by explaining that game details should be fetched separately.

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?

The example queries and the 'covers the week in pinball' framing make the intended use clear, and it explicitly routes agents to get_game_details for a game's editions, prices and design team. It lacks an explicit 'do not use this for X' exclusion versus siblings like search, so it falls short of a full 5.

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

All Kineticist toolsInspect
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.

Resources