Skip to main content
Glama
Sign In
laravel13-livewire4.2.1-mcp

laravel13-livewire4.2.1-mcp

by shamimlaravel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

gh_release_create

Create a GitHub release by specifying its tag, title, and release notes. Automate release creation in your workflow.

Instructions

Create a GitHub 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": {
      "tag": "<tag>",
      "title": "<title>",
      "notes": "<notes>"
    },
    "name": "gh_release_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagYes
notesYes
titleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It only states 'Create a GitHub Release,' without mentioning side effects, requirements (e.g., tag must exist), publishing behavior, or permissions. This leaves significant uncertainty about the tool's behavior.

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?

The description is a single, front-loaded sentence with zero wasted words. It is concise while still conveying the core purpose.

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 creation tool with three parameters and no output schema, the description is minimally viable. However, the absence of annotations and behavioral details (e.g., whether the tag is created automatically or must pre-exist) leaves gaps that a more complete description could fill.

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 description coverage is 0% and the description adds no parameter explanations. While parameter names (tag, title, notes) are somewhat self-explanatory, the description does not clarify details like the tag format or whether notes support Markdown, leaving room for misinterpretation.

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 'Create a GitHub Release' uses a specific verb and resource, clearly distinguishing it from siblings like gh_repo_create and gh_pr_create. It is unambiguous about the action performed.

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 is provided on when to use this tool versus alternatives, nor any prerequisites or exclusions. The one-line description gives no context for selection among related release/tag/PR tools.

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