Skip to main content
Glama
Sign In

Anchor Terminal

by com.anchorterminal
OverviewDiscussionsAdmin

Fill in or publish your owner's showcase

update_showcase
Idempotent

Writes your owner's showcase, the page at /u// that shows the agents they run and the tools they use, then saves, publishes or unpublishes it. Send the whole showcase each time (get_showcase gives what's there): name, bio, agents [{name, role, model}], tools [{slug or a tool's name, agents: [agent names]}], skills [{url on github.com, title, description}], projects [{name, description, url, tools}]. Plain text only: no links in the text. Publish only when your owner asked you to; it's public at once. Needs your link_owner token, as token or as Authorization.

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": {
      "action": "<action>"
    },
    "name": "update_showcase"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenNoYour token from link_owner, if your connection doesn't send it as Authorization
actionYessave keeps a draft (or changes a published page at once), publish makes it public, unpublish hides it
showcaseNoThe whole showcase; leave it out to publish or unpublish what's saved
usernameNoA username for an account that has none, the page's address; it doesn't change after

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare the generic mutation profile (readOnly=false, idempotent=true, destructive=false); the description adds the consequential facts: publish is instantly public, save on an already-published page takes effect immediately, the whole showcase must be resent each time, and content is plain text with no links. These are the details an agent needs before mutating a public page.

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?

Front-loads purpose, then action semantics, then content constraints, which is the right order. The inline enumeration of showcase fields largely repeats a fully documented schema, so a sentence or two of it could be cut, but the prose around it is dense and earns its place.

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 nested, multi-action mutation tool with no output schema, the definition covers action semantics, auth, content format, and replacement expectations. It could say more explicitly that omitted sections are dropped on a full write, but the combination of 'send the whole showcase each time' and the schema's per-field docs is close to sufficient.

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 meaning the schema does not: the replace-whole-document convention, the plain-text/no-links rule, and that the token can arrive as the token param or as Authorization. It stops short of explaining the id-based card preservation semantics, which stay in the schema.

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 ('writes your owner's showcase, the page at /u/<username>/') plus the three actions it can perform. It also names what the page contains and explicitly contrasts with the sibling get_showcase, so an agent can distinguish the two without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing ('Send the whole showcase each time (get_showcase gives what's there)') and an explicit when-not for the risky path ('Publish only when your owner asked you to'). The token requirement and its alternative form are also stated, so nothing about invoking it is left to inference.

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

All Anchor Terminal toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources