Skip to main content
Glama

Enter the sharing code

share_confirm

Re-requests the emailed confirmation code when the entry form or page closed before the user typed it, then lets the user enter it privately without exposing the code.

Instructions

Ask the user again for the code Portward emailed them (when the form or page closed before they typed it). Takes no code: the user types it where you can't see it.

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_confirm"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false), the description discloses the key behavioral fact an agent needs: the tool accepts no code argument and the value is typed out-of-band where the agent cannot see it. That is meaningful context the annotations do not carry. It does not say what the call returns or whether it blocks waiting on the user, which keeps it below a 5.

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?

Two short sentences, front-loaded with the action and followed by the triggering condition. Nothing is redundant or 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?

For a zero-parameter, low-complexity tool with no output schema, the definition covers purpose, trigger, and the out-of-band nature of the input. The only gap is what the agent should expect back after invoking it (confirmation of success vs. another retry), which would help close the loop.

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?

With zero parameters, the baseline is 4, and the description reinforces it by explicitly stating "Takes no code" so the agent doesn't try to fabricate an argument. No further parameter meaning is needed.

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?

The description names a concrete action — re-asking the user for the emailed sharing code — and the parenthetical scoping ("when the form or page closed before they typed it") makes clear this is a re-prompt rather than the initial share flow. It is distinguishable from share, share_mail, and share_link, though it never names a sibling to route against 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?

The trigger condition is stated precisely: use it when the form or page closed before the user typed the code. It stops short of naming alternatives (e.g., what to call if the code was already entered or lost entirely), so the when-not side is left to inference.

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