Skip to main content
Glama

Confirm email for sharing

share_sign_in

Verify a user's email once per device before sharing: Portward sends a code the user enters privately, and their name is shown to recipients.

Instructions

Confirm the user's email for sharing, once per device: Portward emails them a code, and the user types it where you can't see it (never ask for it in the chat). name is how they're shown to the people they share with. Only call this when the user wants to share and gives their own email.

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": {
      "email": "<email>",
      "name": "<name>"
    },
    "name": "share_sign_in"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
emailYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: Portward emails a code, the user enters it out-of-band, the agent must never ask for the code in chat, and confirmation is per device. The annotations only flag it as non-read-only and open-world, so this narrative is doing real work.

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 tight sentences, front-loaded with the action, then the flow, then the guardrail, then eligibility. Every clause adds information the agent cannot get elsewhere.

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 two-parameter tool that kicks off an out-of-band verification flow, the description covers the trigger condition, the user-facing interaction, the agent's constraint, and reuse scope. No output schema exists, and none of the missing pieces are ones an agent needs before calling.

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?

Schema coverage is 0%, so the description must carry the parameters, and it does: `name` is explained as the display name shown to share recipients, and `email` is clarified as the user's own address rather than a recipient's. Format expectations for the email string are still unstated.

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 and resource: confirming the user's email for sharing, with the 'once per device' scoping detail. It does not name a sibling such as share_confirm or share to distinguish itself explicitly, so it stops short of a 5, but the purpose is unambiguous.

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 an explicit call condition: only when the user wants to share and supplies their own email. That covers the when-to-use side well, though it does not name an alternative or say what to do if the user has already confirmed on another device.

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