Skip to main content
Glama

Showcase a lambda

showcase
DestructiveIdempotent

List a lambda on the public showcase page, change its entry, or take it off. Not part of building: only do this when the user asks for it. With only privateKey it returns the current entry. An entry needs a title, a description and a picture (a screenshot or short GIF of the lambda in use); it is listed while the lambda is online. Write plainly and concretely: what it is and what a visitor can do with it. No marketing language, no superlatives, no exclamation marks, no emoji.

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": {
      "privateKey": "<privateKey>"
    },
    "name": "showcase"
  }
}

Input Schema

NameRequiredDescriptionDefault
imageNoThe picture, base64: PNG, JPEG, GIF or WebP, up to the size platform_guide names under showcase. Needed for a new entry; left out, the current one is kept.
titleNoWhat it is, in a few words - 'Pub quiz scoreboard', not 'The ultimate quiz experience'.
removeNoTake the lambda off the showcase instead.
privateKeyYesThe editor key.
descriptionNoOne to three plain sentences on what a visitor can do with it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / description / description
      Previous value: -"One to three plain sentences on what a visitor can do with it. Up to 280 characters."New value: +"One to three plain sentences on what a visitor can do with it."
    • addedInput schema / properties / description / maxLength
      Added value: +280
    • changedInput schema / properties / image / description
      Previous value: -"The picture, base64: PNG, JPEG, GIF or WebP, up to 3 MB. Needed for a new entry; left out, the current one is kept."New value: +"The picture, base64: PNG, JPEG, GIF or WebP, up to the size platform_guide names under showcase. Needed for a new entry; left out, the current one is kept."
    • addedInput schema / properties / remove / default
      Added value: +false
    • changedInput schema / properties / title / description
      Previous value: -"What it is, in a few words - 'Pub quiz scoreboard', not 'The ultimate quiz experience'. Up to 60 characters."New value: +"What it is, in a few words - 'Pub quiz scoreboard', not 'The ultimate quiz experience'."
    • addedInput schema / properties / title / maxLength
      Added value: +60
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true; the description adds real context on top: the entry is listed only while the lambda is online, omitting image preserves the current one, and a remove flag is the takedown path. It does not spell out what happens to the listing when the lambda goes offline or whether removal is reversible, which keeps it at 4 rather than 5.

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?

Mutate/read/remove behavior is front-loaded in the first two sentences. The closing style guidance on tone runs slightly long, but it materially shapes the generated title and description, so it earns its space.

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?

There is no output schema, and the description covers the one return case it can ('returns the current entry'), plus the prerequisites. It lacks detail on the shape of that returned entry or on what the showcase listing looks like, which is a minor gap for a mutation tool.

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 conditional logic the schema cannot express: a new entry requires title, description and picture, while omitting image keeps the existing one. The editorial style constraints also clarify what content the title/description fields expect.

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 opening sentence names a specific verb set (list, change, take off) against a specific resource (public showcase page), so an agent can tell it apart from open_source or deploy without opening the schema. The clause 'Not part of building' further separates it from the code/deploy siblings.

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 an explicit exclusion ('only do this when the user asks for it') and a clear read-mode condition ('With only privateKey it returns the current entry'). It does not name a competing sibling (e.g. open_source) as an alternative, so it stops short of full routing guidance.

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.