Skip to main content
Glama

share_run

Mint a read-only share/embed token for one run — the same token POST /runs/:id/share creates, embedding topology and hop status (never hop content). Requires owner or editor access.

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": {
      "runId": "<runId>"
    },
    "name": "share_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdYesThe run id
ttlDaysNoDurable-link alternative: token lifetime in whole days, 1 to 90 — for demo packs and long-lived shares. Mutually exclusive with ttlSeconds.
ttlSecondsNoToken lifetime in seconds, 60 to 86400 (default 7200)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / ttlDays
      Added value: +{
      +  "description": "Durable-link alternative: token lifetime in whole days, 1 to 90 — for demo packs and long-lived shares. Mutually exclusive with ttlSeconds.",
      +  "type": "number"
      +}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that the token is read-only, exactly which data becomes visible (topology and hop status, never hop content), and the auth requirement. It omits token lifecycle behavior such as idempotency or whether previously minted tokens are revoked, and never states the response shape.

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?

A single front-loaded sentence: purpose first, then REST equivalence, then data-exposure scope, then access requirement. Every clause carries distinct information and nothing is repeated from the schema.

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 three-parameter mutation-style tool with no output schema, the definition covers purpose, precondition and data exposure well. The main residual gap is the return value — an agent cannot tell whether it receives a token string, an object, or a URL — which matters given there is no output schema to fall back on.

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 description coverage is 100%, so runId, ttlDays and ttlSeconds (including ranges, defaults and the mutual-exclusion rule) are already fully documented. The description adds no syntax or selection guidance for the TTL parameters beyond what the schema provides, so the baseline of 3 applies.

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 gives a specific verb and resource ("mint a read-only share/embed token for one run") and pins down the exact data exposure ("embedding topology and hop status (never hop content)"). No sibling tool overlaps with token minting, though the description never explicitly says so, keeping it just short of a 5.

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 supplies concrete usage context: the operation mirrors POST /runs/:id/share and requires owner or editor access, so an agent knows the precondition and the equivalent REST semantics. It stops short of naming a when-not condition or pointing to a sibling alternative, but the context is clear.

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.

Resources