Skip to main content
Glama
Sign In
openserverless-mcp

openserverless-mcp

Official
by apache
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

action_add_secret

Add an existing secret from .env to an endpoint's context using the endpoint path and secret name.

Instructions

Add a secret to an endpoint's context. The secret must exist in .env.

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>",
      "secret": "<secret>"
    },
    "name": "action_add_secret"
  }
}

Input Schema

NameRequiredDescriptionDefault
secretYesThe secret name (e.g. MY_SECRET)
endpointYesThe endpoint path: 'name' (uses v1 package) or 'package/name'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. Only states addition and precondition; no disclosure of side effects, idempotency, or error behavior.

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 short, direct sentences with no wasted words. Information is front-loaded.

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?

Adequate for a simple tool with 2 well-described params and no output schema. Lacks behavioral details like idempotency and error handling, but context signals indicate low complexity.

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% with clear parameter descriptions. The description adds the precondition (secret must exist in .env), which is useful but minimal beyond schema.

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?

Clearly states the verb 'Add a secret to an endpoint's context' and distinguishes from sibling tools that add different resources (e.g., S3, Redis). Could be more explicit about 'endpoint' but still specific.

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?

Implies usage by stating the secret must exist in .env, but no explicit when/when-not guidance or alternatives mentioned. Siblings are distinct, so confusion is low.

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