Skip to main content
Glama

Get my scout invite link

get_scout_invite_link
Read-only

For approved scouts: their personal link to invite other scouts (https://www.productclank.com/scouts?invite=) and share_message, a ready-to-paste invite (the link, plus how to apply from Claude with their code). When the user wants to invite someone, give them share_message verbatim so they can paste it into a chat. Also returns who joined through it and where each one is (building / pending / approved / declined; active = approved and has sent a deal reply). Free, read-only. Invited scouts are reviewed like everyone else. Someone they invite can also apply from their own assistant with apply_as_scout and the invite code.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real context beyond them: invited scouts are reviewed like everyone else, free to call, and each invitee's location in the funnel is defined (building/pending/approved/declined, with active meaning approved plus a sent deal reply). It does not discuss limits on link rotation or what happens if a scout is not approved, which is the remaining gap.

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?

The URL shape and the paste-verbatim instruction are front-loaded, and each following sentence adds new information (what else is returned, status meanings, the sibling route). The status parenthetical is dense but justified since no output schema documents those values.

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?

With no output schema, the description must carry the return-value burden and does: it lists the link, share_message, and per-invitee status including the meaning of 'active'. Nothing an agent needs in order to use the result 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?

There are no input parameters, so there is nothing for the description to disambiguate; it spends its words on return-value semantics instead, which is the right allocation for a zero-argument tool.

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?

The description names a specific resource (the scout's personal invite link and a ready-to-paste share_message) and scopes it to approved scouts, and it clearly separates itself from apply_as_scout, which is what the invitee uses to apply with the code.

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?

It states the triggering condition explicitly ('When the user wants to invite someone'), specifies the action (give share_message verbatim so it can be pasted into a chat), and routes the invitee to apply_as_scout with the invite code rather than coming back to this tool.

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.