Skip to main content
Glama

Get my scout deals

get_scout_deals
Read-only

For approved ProductClank scouts: the founder posts picked for you today, each with the post, why it fits, a drafted opener, its status and your signup/call links. Free, read-only. Use it when the user asks 'what deals do you have for me?'. Show each deal briefly (founder, post, the opener) and let the user pick. A deal matched to them is theirs alone for 12h, then open to every scout. If the user is not a scout (403 not_a_scout), offer to apply them right here with apply_as_scout; scout_not_approved = their application is still in review.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses the 12-hour exclusivity window on a matched deal, that the tool is free, and two concrete failure modes (403 not_a_scout, scout_not_approved) with the interpretation of each. This is exactly the operational context an agent needs to respond correctly when the call fails.

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?

Content is front-loaded: audience and payload come first, then usage trigger, then presentation guidance, then failure handling. A few clauses (the display instruction, the exclusivity rule) could be tightened, but each carries actionable information rather than filler.

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 and no parameters, the description carries the full burden and discharges it: it lists the returned fields, tells the agent how to present them, and covers both error states. An agent could call this tool and handle every documented outcome without further information.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The description correctly avoids inventing inputs and instead spends its words on output shape and error handling.

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 the exact resource (today's founder-post deal picks for ProductClank scouts) and enumerates the payload fields: post, fit rationale, drafted opener, status, and signup/call links. It is clearly distinguishable from siblings such as get_my_submissions or claim_deal, which cover submitted work and claiming respectively.

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?

It gives an explicit trigger phrase ('what deals do you have for me?') and routes non-scouts to apply_as_scout with the specific error codes that should prompt that handoff. It stops short of naming claim_deal as the follow-up action after the user picks, so the next step is only implied by 'let the user pick'.

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.