Skip to main content
Glama

Share a todo as a link

share_todo
Idempotent

Make a read-only web link to one todo and its notes. Anyone with the link can open it without signing in, and it always shows the todo as it is now. Asking again for the same todo returns the same link until it is unshared. Returns the link for the person.

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": {
      "id": "<id>"
    },
    "name": "share_todo"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe todo's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations declare openWorldHint=true and idempotentHint=true, and the description gives them meaning: anyone with the link can open it without signing in, and the link reflects the todo's current state rather than a snapshot. It also discloses the idempotency contract (same link until unshared) and that the link is returned, so callers know the side effect and output without extra fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the action, then access semantics, then idempotency and return value. Every sentence carries information, though the closing 'Returns the link for the person' is slightly redundant with the opening.

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?

For a one-parameter tool with no output schema, the description covers what the tool creates, who can access it, how long it persists, repeated-call behavior, and the return value. Nothing needed to invoke it correctly is missing.

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?

There is a single required parameter whose schema is fully documented as 'The todo's id.' The description only says it acts on 'one todo,' adding no id format or sourcing detail beyond the schema, which is the expected baseline at 100% coverage.

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: 'Make a read-only web link to one todo and its notes.' The phrase 'one todo' implicitly scopes it against list-level sharing, and the return value ('Returns the link') is stated explicitly.

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 clear context for use (public, no-sign-in sharing of a single todo) and describes repeat-call behavior ('Asking again for the same todo returns the same link until it is unshared'), which steers the agent on reuse versus creating new links. It does not explicitly name alternatives such as share_list or unshare_todo, so it stops short of full routing guidance.

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