Skip to main content
Glama
Sign In

Frostbyte

by dev.getfrostbyte
OverviewDiscussionsAdmin

session_end

Record an end-of-session summary on a project's activity feed. Call once when a work session wraps up and no task_complete captured what happened.

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": {
      "projectId": "<projectId>",
      "summary": "<summary>",
      "context": "<context>"
    },
    "name": "session_end"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesExplain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
summaryYesShort summary of what happened in this session
projectIdYesThe project ID this session worked on (must be explicit; not inferred)
filesTouchedNoFiles modified during the session

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-idempotent, non-destructive write to a bounded surface. The description adds meaningful context beyond that: it is an append-only entry to an activity feed, and 'Call once' signals that duplicate calls would create duplicate entries, consistent with idempotentHint=false. It does not say what the tool returns or what happens on a repeat call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler, with the what and the when front-loaded in that order. Nothing is repeated from the annotations or schema.

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 four-parameter write tool with no output schema and full schema documentation, the description covers purpose, timing, and the key exclusion. It leaves the caller's likely follow-up questions unanswered: whether the tool errors on a second call and what the recorded entry looks like.

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 the context parameter carries a detailed usage contract, so the schema already does the heavy lifting. The description only weakly gestures at the summary and project fields, adding no format or constraint details.

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 ('Record an end-of-session summary on a project's activity feed') and explicitly distinguishes itself from the sibling task_complete, so an agent can select it 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?

Gives both the trigger condition ('when a work session wraps up') and the exclusion ('no task_complete captured what happened'), naming the alternative tool that would otherwise apply. Only minor gap is that other siblings such as task_log_decision or signals_capture are not addressed.

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

All Frostbyte 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