Skip to main content
Glama
Sign In

mcp

by io.laraplugins
OverviewDiscussionsAdmin

Get Plugin Details Tool

get-plugin-details-tool

Fetch detailed information for a specific plugin given its vendor/package name, including security advisories, readme, and version history.

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-plugin-details-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
packageNoFull Composer package name in the form "vendor/package".
include_readmeNoWhether to include the full README markdown content in the response.
include_versionsNoWhether to include the versions array in the response.
include_security_advisoriesNoWhether to include security advisory information (CVEs, active advisories) in the response.

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / data / properties / laraplugins_url
      Added value: +{
+  "description": "Human-readable plugin detail page on laraplugins.io for sharing with users",
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties / include_security_advisories
      Added value: +{
+  "default": false,
+  "description": "Whether to include security advisory information (CVEs, active advisories) in the response.",
+  "type": "boolean"
+}
    • addedOutput schema / properties / data / properties / security_advisories
      Added value: +{
+  "properties": {
+    "advisories": {
+      "items": {
+        "properties": {
+          "affected_versions": {
+            "type": "string"
+          },
+          "affects_current_version": {
+            "type": "boolean"
+          },
+          "cve": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "link": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "reported_at": {
+            "type": "string"
+          },
+          "severity": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "is_laraplugins_secure": {
+      "description": "Whether the plugin passes the LaraPlugins Secure badge criteria.",
+      "type": "boolean"
+    },
+    "resolved_count": {
+      "description": "Number of advisories resolved in later or unknown versions.",
+      "type": "integer"
+    },
+    "unpatched_count": {
+      "description": "Number of unpatched advisories affecting the current version.",
+      "type": "integer"
+    },
+    "worst_severity": {
+      "description": "Worst severity among unpatched advisories (critical, high, medium, low).",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": [
+    "object",
+    "null"
+  ]
+}
  3. Changed9 schema fields changed
    • addedInput schema / properties / include_readme
      Added value: +{
+  "default": false,
+  "description": "Whether to include the full README markdown content in the response.",
+  "type": "boolean"
+}
    • addedOutput schema / properties / data / properties / markdown_link
      Added value: +{
+  "description": "Markdown version of the detail page",
+  "type": "string"
+}
    • addedOutput schema / properties / data / properties / optional_fields
      Added value: +{
+  "description": "List of fields available by passing the corresponding include_* parameter",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / data / properties / owner / properties / profile_human_url
      Added value: +{
+  "description": "Human-readable maintainer profile page",
+  "type": "string"
+}
    • addedOutput schema / properties / data / properties / owner / properties / profile_md_url
      Added value: +{
+  "description": "Markdown maintainer profile page",
+  "type": "string"
+}
    • addedOutput schema / properties / data / properties / owner / properties / support_url
      Added value: +{
+  "description": "Sponsor/support URL for this maintainer",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • addedOutput schema / properties / data / properties / readme_markdown
      Added value: +{
+  "description": "Full README markdown content",
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • removedOutput schema / properties / data / properties / short_link
      Removed value: -{
-  "description": "Short link if available",
-  "type": [
-    "string",
-    "null"
-  ]
-}
    • addedOutput schema / properties / data / properties / vendor / properties / support_url
      Added value: +{
+  "description": "Sponsor/support URL for this vendor",
+  "type": [
+    "string",
+    "null"
+  ]
+}
  4. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations carry only a title, so the description bears the full burden. The verb 'Fetch' signals a read-only, non-destructive lookup and the description enumerates what is returned, but it says nothing about behavior when the plugin is unknown, response size, or any rate/auth constraints.

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?

A single front-loaded sentence that names the action, the key input, and the payload. No filler, no redundancy with the schema or title.

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

Completeness4/5

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

With a full output schema and 100% covered parameters, the description only needs to justify why an agent would call this tool, which it does. Its one gap is routing guidance relative to the three sibling tools, which it leaves to inference.

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 the schema already documents all four parameters including the vendor/package format and the three opt-in booleans. The description adds only a light grouping of those flags into returned content categories, so the baseline of 3 applies.

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?

States a specific verb and resource (fetch detailed information for a plugin) and specifies the identifier (vendor/package name), which distinguishes it from the search-oriented siblings. It does not explicitly name those siblings, but the singular-lookup framing is clear enough for an agent to separate it from search tools.

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?

Usage is implied rather than stated: the tool takes a full package name, so an agent can infer it is the follow-up to a search that already produced an identifier. There is no explicit when-to-use, no exclusions, and no mention that search-plugin-tool should be used first to discover the package name.

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

All mcp toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources