Skip to main content
Glama

Share panel: read the link

share_link
Read-only

Reads a newly created share's link and extracts its # key so the share panel can display and copy it. App-only; the model never sees this result.

Instructions

The share panel reads a new share's link (its # part is the key) to show and copy. App-only: the model never sees this tool or its result.

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": {
      "share_id": "<share_id>"
    },
    "name": "share_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
share_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds useful context beyond that — the link fragment ('# part') is the key and the tool is app-only — but it does not cover permissions, error behavior, or the meaning of share_id.

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?

Two compact sentences, front-loaded with the action and followed by the app-only qualifier. No padding.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read-only tool the definition is nearly sufficient, but it omits any explanation of the required share_id and leaves the app-only note unexplained in agent terms.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With a single required parameter and 0% schema description coverage, the description should explain share_id. Instead it describes the link's fragment, not the identifier, so the agent gets no added meaning for the parameter.

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?

States a specific verb ('reads') and resource ('a new share's link') plus the outcome ('to show and copy'). It does not name an alternative sibling, but the narrow 'share panel' scope makes its role distinguishable.

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

Usage Guidelines2/5

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

No explicit when-to-use or when-not guidance; the only scoping statement is 'App-only: the model never sees this tool or its result', which is a visibility constraint rather than usage guidance. The agent is left to infer it belongs to the share-panel flow.

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