Skip to main content
Glama
Sign In

Jam

by dev.jam
OverviewDiscussionsAdmin

updateJam

DestructiveIdempotent

Update a Jam bug report: rename it, rewrite its description, or move it between folders. Every field is optional — only the ones you pass are changed. Use folder name, folder ID, folder short ID, or "root" to move to the root level. Editing the title or description requires an Admin or Creator role.

Input Schema

NameRequiredDescriptionDefault
jamIdYesJam identifier — a UUID or a jam.dev URL
titleNoNew title for the Jam
folderNoTarget folder: folder name, folder ID, folder short ID, or "root" to move to root level
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.
descriptionNoNew description for the Jam, in Markdown format. To mention a teammate and notify them, write `@[Their Name](user:<userId>)` — get the userId from listMembers. A plain `@name` is left as ordinary text and notifies nobody.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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

A3.8/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is structured. The description adds genuine context: partial-update semantics (only passed fields change) and the Admin/Creator role requirement for title and description edits. However, it never addresses the destructiveHint — that rewriting a description overwrites prior content — nor what the call returns.

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?

Three sentences, front-loaded with the capability then the partial-update rule then the permission caveat. No filler. The folder-resolution sentence is verbatim schema duplication and could be cut without loss.

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 mutation tool with six parameters, no output schema, and rich annotations, this covers the essentials: what can change, that changes are partial, and who is allowed. The omission of return shape is acceptable given no output schema, but the unexplained destructiveHint leaves a small gap.

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

Parameters2/5

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

Schema coverage is 100%, so the description is held to the baseline, but it largely restates schema text (the folder name/ID/short ID/"root" resolution is copied from the parameter description). It adds nothing about jamId accepting a UUID or jam.dev URL, and says nothing about intent or llm_model. At best it reinforces a single parameter.

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 names a specific verb and resource ("Update a Jam bug report") and enumerates the three operations it supports: rename, rewrite description, move between folders. An agent can immediately distinguish it from deleteJam, updateFolder, and listJams without consulting 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 Guidelines4/5

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

It makes the usage model explicit: every field is optional, only passed fields change, and folder accepts a name/ID/short ID/"root". It also states the role prerequisite for title/description edits. It stops short of naming alternatives (e.g. that folder management itself belongs to updateFolder/createFolder) or stating when not to use it.

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