Skip to main content
Glama

list_plugin_base_bundle

Read-only

Describe the MCP local sandbox + preferred FILE-based plugin layout. Agents should write real files (Scene.tsx, schema.json, package.json, components/*), then use pack_plugin_dir and propose_plugin_preview. JSON modules are only for the API edge. Does NOT change the main app create path.

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": "list_plugin_base_bundle"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds a useful scope exclusion ('Does NOT change the main app create path') that tells the agent this is purely informational rather than an alternative creation route. It does not describe the shape or granularity of what is returned.

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?

Four short sentences, front-loaded with the core purpose before the workflow guidance and the scope caveat. The file-name examples earn their place by being concrete; nothing is padded or repetitive.

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 zero-parameter, read-only informational tool with no output schema, the description should convey what an agent gets back. It states the topic (sandbox layout and file conventions) and the follow-up tools, but never indicates the form of the answer (rules, directory tree, example scaffold), leaving the agent guessing how actionable the output will be.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. No parameter-related claims are made or needed.

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?

The description uses a concrete verb ('Describe') and a concrete resource ('the MCP local sandbox + preferred FILE-based plugin layout'), and it names the concrete artifacts involved (Scene.tsx, schema.json, package.json, components/*). It is slightly at odds with the tool name 'list_plugin_base_bundle', which implies enumerating a bundle, so an agent scanning names could mispredict the payload, but the prose itself is specific.

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?

It gives a clear downstream workflow: write real files first, then use pack_plugin_dir and propose_plugin_preview, and it warns that JSON modules belong only at the API edge. What it lacks is an explicit 'call this before you start writing files' instruction, so the trigger condition for this tool is only implied by ordering.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources