Skip to main content
Glama
Sign In

mcp-server

by io.alterlab
OverviewDiscussionsAdmin

Hands Share Run

alterlab_hands_share

Offer to share a completed run. action=preview returns the exact public page (scrubbed timeline, receipt, price, remix link) and stores nothing; show it to the user. action=publish makes it public at alterlab.io/r/ and needs approve=true, which only the user may give after seeing the preview. Pages are noindex unless indexable=true. action=unpublish makes the link return 404; publish again to reuse the slug.

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": {
      "run_id": "<run_id>"
    },
    "name": "alterlab_hands_share"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoOptional page title
actionNoDefault preview
run_idYesThe completed run
approveNoPublish: the user approved this public page
indexableNoLet search engines index the page; default false

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it discloses that preview is side-effect free ('stores nothing'), that publish requires an explicit user-granted approve flag, that pages are noindex by default unless indexable=true, and that unpublish leaves a 404 while the slug remains reusable — so the mutation is effectively reversible, consistent with destructiveHint=false and idempotentHint=false.

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 dense sentences, front-loaded with the purpose, then each action in sequence, then the indexing and slug-reuse caveats. Every sentence carries an operational fact and none repeat the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 compensates by stating what the preview page contains (scrubbed timeline, receipt, price, remix link) and that publish yields a public alterlab.io/r/<slug> URL. For a five-parameter, three-action tool this covers everything needed to call it correctly.

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; the description adds real meaning on top by explaining the semantic intent of action values and the constraint that approve is a user-consent signal that must follow a preview. It does not add format detail for title or run_id, but those are already fully documented in the 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?

The description opens with a specific verb+resource ('Offer to share a completed run') and enumerates the three action values with their concrete effects (preview stores nothing, publish creates alterlab.io/r/<slug>, unpublish 404s). It is clearly a sharing tool, distinct from alterlab_hands_run and alterlab_run_approve, though it never names those siblings to rule them out explicitly.

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?

It gives an explicit workflow: call action=preview and show the result to the user, and only then may publish be used with approve=true, which 'only the user may give after seeing the preview'. That is a clear when-to-use-each-action rule plus a hard gate, leaving little to inference.

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

All mcp-server toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources