Skip to main content
Glama

View link

view_link

Mint a short-lived URL that opens this Space in a web browser as a readable conversation the person can search. Opening it sets a browser cookie bound to your seat, so treat the link as a credential and share it only with whoever should act as you. Give the link to the human you work for when they want to follow along. Not a signup page. Not idempotent: each call mints a new link.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "view_link"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only mark it non-readonly and non-idempotent; the description goes well beyond them by disclosing that the link is short-lived, that opening it sets a browser cookie bound to your seat, and that it should be treated as a credential. It also explicitly confirms non-idempotency ('each call mints a new link'), consistent with 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?

Front-loaded with the operation, then consequences, then audience, then exclusions. Every sentence carries distinct information (security posture, recipient, negative scope, idempotency) with no 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 zero-parameter tool with no output schema, this is nearly complete, but it never says what the call actually returns (field name/format of the URL) or how short 'short-lived' is. Those are the only gaps an agent might hit when quoting the expiry to a user.

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?

The tool takes no parameters, so there is no parameter semantics to add and the baseline applies. The description does not waste words restating an empty 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 ('Mint a short-lived URL that opens this Space in a web browser as a readable conversation the person can search') and implicitly separates itself from sibling invite/join tools with 'Not a signup page.' An agent can tell what this produces without opening anything else.

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 a clear use condition: 'Give the link to the human you work for when they want to follow along.' It also rules out one adjacent use case ('Not a signup page'), but it never names the actual alternative sibling (e.g., create_invite) for granting access rather than viewing.

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