Skip to main content
Glama
Sign In
openserverless-mcp

openserverless-mcp

Official
by apache
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

action_new

Create a new API endpoint: generate an action folder with main.py and a module file, optionally public or private.

Instructions

Create a new API endpoint. Creates the action folder with main.py and module file.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "endpoint": "<endpoint>"
    },
    "name": "action_new"
  }
}

Input Schema

NameRequiredDescriptionDefault
publicNoWhether the action is public (API endpoint). Defaults to true. Set false for private actions (e.g. init package).
endpointYesThe endpoint path: 'name' (uses v1 package) or 'package/name'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses file creation but does not mention permissions, idempotency, or what happens if the endpoint already exists. Minimal transparency.

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?

Two sentences, front-loaded with the main purpose, no wasted words. Efficient and clear.

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?

No output schema, so description should hint at return values or errors; it does not. For a creation tool, knowing what is returned is useful. Adequate but not complete.

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 coverage is 100%, so baseline is 3. Description adds no additional meaning beyond the schema's parameter descriptions. No value added.

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 creates a new API endpoint and specifies the exact files created (action folder, __main__.py, module file). It is distinct from sibling tools which add integrations or invoke actions.

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 for creating new endpoints but does not provide explicit when to use, when not to use, or alternatives. It's adequate but lacks guidance.

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