Skip to main content
Glama

Share a pull

share

Email a teammate an encrypted link to a pull from history, with expiring access, column visibility controls, blocked columns excluded, and optional CSV download.

Instructions

Share a pull from history with a teammate by email: the table is encrypted on this machine and the link is shown to the user in the Portward share panel to copy and send (or open in their mail app from there; without a panel a draft opens in their mail app). You never see the link. The teammate opens it with a code emailed to them; it expires after days (7 unless the user asks for longer: up to 90 where the plan allows). Blocked columns are never included. options sets what the teammate sees of each column, as the user chooses: "include" (the default for columns not named), "hide", "anonymise" (each value becomes a code, the same value the same code within this share only) or "totals" (only sums per group of the other columns, groups of fewer than 5 rows left out). Ask the user which they want; don't choose for them. allow_download (default false: view only) lets the teammate download the shared table as a CSV; leave it false unless the user asks for the teammate to be able to download it. It can't be changed after sharing. Only call this when the user asks to share and names the teammate.

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": {
      "pull_id": "<pull_id>",
      "recipient": "<recipient>"
    },
    "name": "share"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
optionsNo
pull_idYes
recipientYes
allow_downloadNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations only mark it as a non-read-only, open-world, non-destructive action; the description adds substantial context beyond that: local encryption, the agent never sees the link, recipient access via emailed code, expiry behavior, blocked columns never included, and allow_download being immutable after sharing. Minor gap: it does not say what the tool returns to the agent on success (e.g., confirmation id/status).

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?

Front-loaded with the core action and dense with useful detail, but one sentence about the panel/mail-app fallback is long and slightly convoluted, and the expiry note is tucked mid-paragraph. Little is wasted, though the panel aside could be tightened.

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 mutation with an open-world side effect, no output schema, and 0% schema coverage, the description covers delivery mechanism, secrecy of the link, expiry, column blocking, per-column visibility modes, and immutability of download settings. Nothing an agent needs 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.

Parameters5/5

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

Schema coverage is 0%, so the description must carry parameter meaning and it does: days (default 7, plan-dependent cap of 90), options with all four modes and their semantics including same-code-within-share and k-anonymity suppression under 5 rows, and allow_download (default false, CSV, immutable afterwards). Only pull_id and recipient rely on their self-evident names.

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, resource, and channel: 'Share a pull from history with a teammate by email.' It also distinguishes the tool from the adjacent share_* workflow by explaining that the link is delivered through the user's panel/mail app rather than returned to the agent.

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

Usage Guidelines5/5

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

Gives a hard precondition ('Only call this when the user asks to share and names the teammate') and explicit user-interaction rules ('Ask the user which they want; don't choose for them', 'leave it false unless the user asks'). Both when-to-use and when-not-to-act are stated.

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