Skip to main content
Glama
Sign In
forgejo-mcp

forgejo-mcp

by jerdog
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get latest release

get_latest_release
Read-only

Fetch a repository's current published release by owner and repo name to check version tags, assets, notes, or release metadata.

Instructions

Get the latest published release.

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": {
      "owner": "<owner>",
      "repo": "<repo>"
    },
    "name": "get_latest_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesRepository name
ownerYesRepository owner (user or organization)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered structurally. The description adds nothing beyond that — it does not clarify what 'latest' means (newest by date vs. highest semver), whether drafts/prereleases are excluded, or what the response contains.

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?

A single front-loaded sentence with no waste or filler. Its brevity is appropriate, though there was room to add one disambiguating clause without bloat.

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

Completeness3/5

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

For a simple two-parameter read with full annotations and no output schema, the definition is minimally adequate. It leaves open the meaning of 'latest' and its relationship to list_releases/get_release_by_tag, which is the main remaining gap.

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%, so both parameters (owner, repo) are already documented in the schema. The description contributes no additional parameter meaning, which is acceptable here but yields only the baseline score.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clear verb+resource: 'Get the latest published release' tells the agent exactly what is retrieved. It does not name its nearest siblings (list_releases, get_release_by_tag), so an agent must infer the difference from the name alone.

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

Usage Guidelines2/5

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

No guidance on when to pick this over list_releases or get_release_by_tag, and no mention of required owner/repo context or prerequisites. The agent gets a purpose but no routing logic.

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

Deploy Server

Other Tools