Skip to main content
Glama

Share the list as a link

share_list
Idempotent

Make a read-only web link to the person's whole open list (titles, stars and the first line of each todo's notes). Anyone with the link can open it without signing in, and it always shows the list as it is now. Returns the same link until it is unshared.

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": "share_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that anyone can open the link without signing in (an access-control consequence), that it is read-only, that it reflects live list state rather than a snapshot, and exactly which fields are exposed. That is precisely the context openWorldHint=true and idempotentHint=true leave unexplained.

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, front-loaded with the action and its scope, then access model, then return behavior. Nothing is redundant and the exposed-data list is packed efficiently into one parenthetical.

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 comes back ('the same link until it is unshared'). For a zero-parameter, no-annotation-burden tool, nothing an agent needs in order to call it correctly is missing.

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 zero parameters, so there is nothing to disambiguate and the baseline applies. The description correctly spends its words on scope and effects instead of inventing parameter detail.

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?

Uses a concrete verb and resource ('Make a read-only web link to the person's whole open list') and immediately bounds the payload (titles, stars, first line of notes), which implicitly contrasts with the per-item share_todo sibling. An agent can tell exactly what this produces without opening any schema.

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?

The 'whole open list' scope implies when this is preferable to a single-item share, and 'until it is unshared' hints at the unshare_list counterpart, but there is no explicit when-to-use/when-not statement or named alternative. Usage must be inferred rather than read.

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