Skip to main content
Glama

webbersites-x402-data-api

by io.github.webberdesign

post_lint_php

PHP lint: POST {code}, get the bugs back with line numbers. Deterministic static analysis — code is never executed, no AI. Catches SQL injection (request data interpolated into query strings), the removed mysql_* API, unbalanced braces, '+' string concat, = vs == in conditions, type-juggling loose comparisons, eval/extract on request data, unused variables, leftover var_dump. Understands PHP tags, heredocs, interpolation. Max 128 KB. ($0.002 per call, paid via x402)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYesPHP source to lint, max 128 KB

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countsNo
issuesNo
syntaxNo
verdictNo
languageNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The description provides extensive behavioral details: deterministic static analysis, no execution, no AI, specific bugs caught, max size, and pricing. This adds significant value beyond 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?

The description is a single paragraph but efficiently packs purpose, capabilities, and constraints. It is slightly lengthy but every sentence adds value.

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?

Given the simple input (one string) and existing output schema, the description covers all necessary context: purpose, behavior, specific detections, limitations, and cost. It is fully adequate for an agent to select and invoke this tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The sole parameter 'code' is described in both schema and description as PHP source up to 128 KB. Schema coverage is 100%, and the description adds the size limit, which is useful but minimal extra.

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 it lints PHP code to find bugs with line numbers. It specifies the input is PHP source code, distinguishing it from sibling lint tools for other languages.

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?

The description implicitly indicates use for PHP linting, but does not explicitly state when not to use or suggest alternatives. It does mention a 128 KB limit, which is helpful.

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

All webbersites-x402-data-api toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools have distinct purposes, but the SEO-related tools (head_check, full_audit, site_audit, etc.) overlap in scope, potentially causing confusion despite clear descriptions.

Naming Consistency5/5

Tool names consistently follow a get_/post_/delete_ verb pattern with descriptive noun phrases (e.g., get_seo_head_check, post_store_collection), with no mixing of naming conventions.

Tool Count2/5

With 46 tools covering a wide breadth of domains (SEO, accessibility, music, crypto, linting, etc.), the count is excessive for a single server, feeling unfocused and heavy.

Completeness4/5

The tool set covers most core operations for each sub-domain, but minor gaps exist (e.g., missing update for datastore, limited music operations).

Resources