Skip to main content
Glama
Sign In

Jam

by dev.jam
OverviewDiscussionsAdmin

getDetails

Read-onlyIdempotent

The entry point for any Jam: call it first. Returns what the Jam is (title, description, author, page, browser and OS), its comments and links, the recording's timeline in time order, and a guide to what else the Jam holds and which tool reads it. A comment pinned to a playback time shows it as [M:SS]. format: "json" returns the structured payload instead of the text (IDs, folder, event counts, processing status, and on a video Jam a public 360p thumbnailUrl for each pinned comment, to share with a person). Once you find the cause or fix it, post one createComment that says so and mentions the creator as @[Name](user:<author.id>), unless the creator is the user you act for. Then call submitFeedback once with this Jam's jamId and evidence set to the Jam data that led you there. The links list the Jam's resources (pull requests, tickets, docs) and related Jams; when you fix or prove something, add the pull request with addResource and mark a proof or fix Jam as related to the bug Jam with markRelated.

Input Schema

NameRequiredDescriptionDefault
jamIdYesJam identifier — a UUID or a jam.dev URL
formatNoDefault "text". "json" for the structured payload a program parses.
intentNoIn 15-30 English words, your larger task and why this call helps it. People by role ("a customer"); no argument values or secrets.
llm_modelNoYour exact model id from your system prompt, or "unknown". Never guess.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / format
      Added value: +{
+  "description": "Default \"text\". \"json\" for the structured payload a program parses.",
+  "enum": [
+    "text",
+    "json"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / intent / description
      Previous value: -"In 15-30 words, say what larger task you are working on and why this tool helps it. Refer to people and companies by role (\"a customer\"), and leave out argument values and secrets. Use English. Example: \"Debugging a checkout failure a customer reported, checking which network request returned the 500.\""New value: +"In 15-30 English words, your larger task and why this call helps it. People by role (\"a customer\"); no argument values or secrets."
    • changedInput schema / properties / llm_model / description
      Previous value: -"The exact model identifier you are running as, from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Pass \"unknown\" if you are not certain; never guess."New value: +"Your exact model id from your system prompt, or \"unknown\". Never guess."
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Beyond the readOnly/idempotent annotations, it discloses the rendering convention (`[M:SS]` for pinned comments), what the json format adds (IDs, folder, event counts, processing status, 360p thumbnailUrl per pinned comment), and that it acts as a first-pass overview that points to other tools. It does not cover pagination/truncation limits on large Jam timelines, which keeps it short of a 5.

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?

Front-loaded with the single most important fact (call it first) and the return summary, with format behavior positioned right after. The closing workflow sentences about createComment/submitFeedback/addResource are dense but partly choreography that belongs to those tools' definitions, making the tail heavier than necessary.

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?

With no output schema, the description carries the return-value burden and does so thoroughly — text shape, json shape, and the `[M:SS]` annotation convention. For a read-only 4-parameter overview tool whose annotations already state the safety profile, nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3; the description earns a bump by explaining the consequence of `format: "json"` in terms of concrete payload contents (IDs, folder, event counts, thumbnailUrl) rather than repeating the schema's terse "structured payload a program parses". jamId and intent/llm_model semantics are left entirely to the schema, which is acceptable given full coverage.

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 a specific verb and resource ("The entry point for any Jam") and enumerates the returned facets — title, description, author, page, browser/OS, comments, links, timeline — which unambiguously separates it from siblings like listJams, getEvents, or getMetadata. An agent can identify the tool's role without opening the schema.

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

Usage Guidelines5/5

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

Explicit ordering guidance ("call it first") plus follow-on routing to createComment, submitFeedback, addResource, and markRelated with the conditions that trigger each. It also names an exclusion: don't mention the creator if the creator is the user you act for.

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

All Jam toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources