Skip to main content
Glama
Sign In
TeamOnly

TeamOnly

by sohelsd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Save a secret

set_secret
Idempotent

Saves an API key or password as an app secret so deployed TeamOnly apps can read it at runtime with ctx.secrets.get(NAME). Ask the user for the value; never hardcode it.

Instructions

Saves a secret (API key, password) for the deployed app. The app reads it with ctx.secrets.get(NAME). Names are UPPER_SNAKE_CASE. Ask the person for the value; never put it in code.

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": {
      "name": "<name>",
      "value": "<value>"
    },
    "name": "set_secret"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYese.g. OPENAI_API_KEY
valueYesThe secret value
directoryNoAbsolute path of the app's folder (the one with teamonly.json). Defaults to the folder the server started in.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare openWorldHint and idempotentHint, so the description's added value is the consumption path (ctx.secrets.get(NAME)) and the naming convention, both useful context. It stops short of saying what happens when a name already exists (overwrite vs. error) or whether a redeploy is needed for a running app to pick up the new value.

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?

Four short sentences, each carrying distinct information: what it does, how the app reads the value, the naming rule, and the security instruction. The core action is front-loaded with zero filler.

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?

For a simple three-parameter tool with no output schema, the description covers purpose, naming, consumption, and the sourcing rule. The remaining gap is lifecycle behavior: whether the secret is available to an already-running deployment or requires a redeploy, and what happens on a name collision.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds a normative constraint the schema lacks: names must be UPPER_SNAKE_CASE, not merely exemplified as OPENAI_API_KEY. It says nothing extra about the directory parameter beyond what the schema already documents.

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?

States a specific verb and resource (saves a secret) with concrete examples of what a secret is (API key, password) and the scope (for the deployed app). No sibling tool covers secrets, so there is nothing to disambiguate against, and an agent can act on this immediately.

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?

Gives explicit operational guidance: ask the person for the value and never hardcode it in code, which tells the agent how to source the input rather than guessing. It does not name alternatives or when-not-to-use, but no sibling covers this capability.

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