Skip to main content
Glama
Sign In

Release Notes Index

by sh.releases
OverviewDiscussionsAdmin

Get personalized feed

get_personalized_feed
Read-onlyIdempotent

Your personalized release feed — recent releases from the organizations and products you follow, newest first. Requires a signed-in user. Same item shape as get_latest_releases, scoped to your follows. Each item prints URL: (the original source — cite that) before Web: (the releases.sh copy), when present.

Cursor-paginated: pass cursor from a prior response's _meta.pagination.nextCursor and optional limit (1–100, default 30).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_personalized_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoEntries per page (1–100). Defaults to 30.
cursorNoOpaque cursor from a previous page's `_meta.pagination.nextCursor`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. Changed2 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "Opaque cursor from a previous page's `_meta.pagination.nextCursor`.",
+  "type": "string"
+}
    • removedInput schema / properties / page
      Removed value: -{
-  "description": "1-based page number. Defaults to 1.",
-  "maximum": 9007199254740991,
-  "minimum": 1,
-  "type": "integer"
-}
  3. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavior: the signed-in-user auth requirement, newest-first ordering, the citation guidance that URL: (original source) prints before Web: (the mirror copy), and cursor pagination semantics. This is context an agent cannot derive from the annotations.

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-loads the identity and scope in the first sentence, then layers auth, item shape, citation guidance, and pagination. Every sentence earns its place, though the URL:/Web: detail is denser than strictly necessary for tool selection.

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: it names the item shape by reference to a sibling and describes the URL:/Web: fields. Auth, ordering, and pagination are all covered, leaving nothing an agent needs missing.

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 description coverage is 100% — both `limit` (1–100, default 30) and `cursor` (opaque, from `_meta.pagination.nextCursor`) are already documented in the schema, and the description largely restates them. No additional format or edge-case meaning is added, so the baseline 3 applies.

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 ('personalized release feed — recent releases from the organizations and products you follow') with ordering ('newest first'). It explicitly distinguishes itself from the sibling get_latest_releases by scoping to follows, so an agent can route between them without opening schemas.

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?

Gives a clear precondition ('Requires a signed-in user') and clarifies the relationship to get_latest_releases ('same item shape ... scoped to your follows'), which is the main alternative an agent would weigh. It does not spell out an explicit when-not-to-use or name other feed-like siblings, so it stops short of a 5.

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

All Release Notes Index 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