Skip to main content
Glama
Sign In

Nutcracker

by com.heynutcracker
OverviewDiscussionsAdmin

Share link

share_link

Publish a doc, presentation or storyboard: returns its public read-only link, which anyone with the link can open without an account. Returns the existing link when there is one. The link shows in the doc Share panel.

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

Input Schema

NameRequiredDescriptionDefault
doc_idYesA doc id from get_task or list_space.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the security-relevant consequence (anyone with the link can open it without an account) and idempotent behavior (returns the existing link when one exists). It does not say what permissions are required or whether prior sharing settings are altered, which is the main remaining gap for a mutating, open-world tool.

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?

Three short sentences, all load-bearing: purpose, access semantics, idempotency, and where the result surfaces in the UI. The verb leads and nothing is padded.

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?

With no output schema, the description correctly carries the return-value burden by naming the public read-only link and the reuse-existing behavior. Only prerequisites and side effects on the document's sharing state are left unstated.

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 coverage is 100% and the single doc_id parameter is already documented with its source tools. The description adds only an indirect hint that doc_id may refer to a doc, presentation, or storyboard, which is marginal extra meaning.

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 (Publish) and the resource types it applies to (doc, presentation, storyboard), plus what it returns. An agent can tell this apart from read_doc or export without opening the schema, though it never names its true inverse sibling (unshare).

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

Usage Guidelines3/5

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

Usage is implied rather than stated: an agent must infer 'use this when you want a public link.' There is no explicit when-not guidance and no pointer to unshare for revoking a link, which is the one alternative an agent would most plausibly need.

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

All Nutcracker 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