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

laravel13-livewire4.2.1-mcp

by shamimlaravel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_open_bugs

Retrieve all open (unfixed) bugs from your Laravel/Livewire project. Filter results by severity: all, critical, high, medium, low.

Instructions

Get list of all open (unfixed) bugs.

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_open_bugs"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The verb 'Get' implies a read-only operation, but the description does not explicitly confirm non-destructive behavior, mention output format, or describe any side effects. It provides minimal transparency beyond the tool's name.

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, concise sentence with no wasted words. It front-loads the purpose and is easy to parse. It earns its place as a clear, crisp definition.

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

Completeness2/5

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

Given the simplicity of the tool (one optional parameter, no annotations, no output schema), the description is still incomplete. It omits any mention of the filter parameter, does not clarify relationship to sibling get_fixed_bugs, and provides no information about return values. It lacks the full context needed for an agent to use it confidently.

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% (no parameter descriptions). The description does not mention the 'filter' parameter, its enum values, or the 'all' default. Although the schema provides an enum and default, the description fails to compensate for the lack of schema descriptions. The parameter semantics are not communicated at all.

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 clearly states the verb 'Get' and the resource 'list of all open (unfixed) bugs.' It explicitly specifies 'unfixed,' which distinguishes it from the sibling tool get_fixed_bugs. This is a specific, non-tautological statement of purpose.

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

Usage Guidelines3/5

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

The description implies usage context by specifying 'open (unfixed) bugs,' which suggests it is not for fixed bugs. However, it does not explicitly name alternatives like get_fixed_bugs or state when to use this tool over other bug-related tools. Guidance is implied, not explicit.

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