Skip to main content
Glama

Open a new alert in Poacher

start_alert_in_app
Read-onlyIdempotent

Make a link that opens Poacher’s alert builder with a search already filled in. Give the link to the person: they sign in (or sign up), check the source and approve the price in Poacher. Use this when the person wants to finish in the app, or when this connection lacks monitoring:manage. With monitoring:manage, you can create and start the alert yourself instead (see the server instructions). The link saves and charges nothing until the person finishes in the app.

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

Input Schema

NameRequiredDescriptionDefault
briefNoWhat the person wants, in their words: item, condition, price ceiling, place. Poacher uses this to judge matches.
source_urlNoThe public search or listing page to watch, for example an eBay or AbeBooks search results URL.

Output Schema

NameRequiredDescriptionDefault
dataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare readOnlyHint and non-destructive, and the description adds real context beyond them: the link saves and charges nothing until the human signs in and approves the price, and the recipient must authenticate. It does not cover link lifetime or what the returned link contains, which the output schema presumably handles.

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?

Four short sentences, front-loaded with the core action, then the handoff flow, then the permission branch, then the cost guarantee. Nothing is redundant, though the permission aside could be trimmed slightly.

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?

Covers the handoff model, permission gating, and no-charge-until-approved behavior; return values are covered by the output schema. Missing only minor operational detail such as link expiry or what the receiving person sees if they decline.

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?

Schema coverage is 100% with descriptions for both brief and source_url, so the schema carries parameter meaning. The description adds no format or content guidance for these two fields, so baseline 3 applies.

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 artifact: it makes a link that opens Poacher's alert builder with a search pre-filled. It implicitly separates itself from approve_alert_creation / quote_alert_creation by clarifying that with monitoring:manage you create and start the alert yourself rather than producing a handoff link.

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?

Explicit when-to-use: the person wants to finish in the app, or the connection lacks monitoring:manage. It also states the alternative path available when monitoring:manage is present, so the agent can route correctly.

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