Loading ToolBench

Reading the current corpus…

laravel-agentic MCP server · F · ToolBench

laravel-agentic

An agent-native action layer for Laravel. Define an action once; expose it to humans and agents everywhere — with approvals and audit built in.

2026-07-28+STDIO2 tools

43/100

Definition Quality41

Protocol Readiness50

Supportability40

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence

Current-spec patterns detected

Summary

Two tools with minimal documentation. Tool names lack action verbs (refund-invoice is hyphenated, lookup is generic). Schemas present but sparse. No output schema documentation. No error handling guidance. No composition hints. This server falls well below production baseline.

Tools (2)

lookupread onlyauthsource verified38/100

Read-only lookup action

refund-invoicewriteauthsource verified43/100

Refund an invoice to the original payment method.

Issues (5)

CRITICALtool-description ↗

All parameters lack descriptions. 'invoiceId', 'amount', and 'message' have no guidance on format, constraints, or purpose. Rubric requires 100% of A+ tool params to have descriptions.

refund-invoicelookup

HIGHtool ↗

Tool names lack action verbs. 'refund-invoice' uses a hyphen (non-standard); 'lookup' is generic and ambiguous. Rubric baseline: 90% of A+ tools start with action verbs (get, create, update, delete, search, list, send). 'lookup' does not signal what is being looked up or what the result is.

refund-invoicelookup

HIGHtool ↗

No output schema documented. LLMs cannot plan downstream calls or extract required fields. Rubric: 100% of A+ tools have documented return types.

refund-invoicelookup

HIGHrecovery-guide ↗

No error handling guidance. If refund fails (insufficient funds, invalid invoice), the LLM has no recovery path. Rubric requires error responses to tell the agent what to do next.

Recommendations

Add parameter descriptions to all inputs. Example: 'invoiceId' → 'The numeric ID of the invoice to refund (e.g. 12345). Must be a positive integer.' 'amount' → 'The amount to refund in USD (0.01 - invoice total). Defaults to full invoice amount if omitted.'
Rename 'lookup' to a verb_noun pair reflecting what is looked up. E.g. 'search_messages', 'get_user_by_email', 'find_transaction'. Current name is too generic.
Rename 'refund-invoice' to 'refund_invoice' (underscore, not hyphen) and add a description explaining the operation is irreversible and requires approval.
Document output schemas for both tools. Example for refund_invoice: '{refund_id: string, status: enum[pending|completed|failed], amount: number, created_at: ISO8601}'.
Add error handling guidance. Example: 'If invoice not found, try search_invoices() with customer email. If refund fails due to insufficient funds, contact support.' This guides the LLM's recovery path.

Score history

Overall score trend

First recorded score · v2 rubric

43/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	F	43	2026-07-28+	v2