Skip to main content
Glama

Submit my scout application

submit_scout_application
Idempotent

Submit the drafted scout profile for ProductClank's review, with the user's edits. Free. Only call it after the user has seen the draft and said it is right. profile = only the fields they changed. boundaries = how they want to work: channels (public_replies, dms, intros) and dealsPerDay (1, 3 or 5); required the first time. After it, tell the user a person reviews every scout; on approval they join the ProductClank Scouts squad and their deals start.

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

Input Schema

NameRequiredDescriptionDefault
profileNoOnly the fields the user changed. Everything else keeps the drafted profile.
boundariesNoRequired on the first submit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing cost (free), the human review step, and the downstream consequence of approval (joining the ProductClank Scouts squad, deals starting). It also prescribes post-call behavior: tell the user a person reviews every scout. Annotations only cover safety/idempotency, so this adds real operational context.

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?

Front-loaded with the action and the precondition, and every sentence carries information. The telegraphic fragments ('Free.', 'required the first time') read choppy but are not wasteful.

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 nested two-object mutation with no output schema, it covers the precondition, the partial-update semantics, and the outcome. It omits what happens on rejection or whether a resubmission is expected, despite the idempotent hint.

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 100%, so the baseline is 3, but the description adds intent: profile means only the fields the user changed, and boundaries means how they want to work, enumerating channels and dealsPerDay values. It largely mirrors the schema descriptions, which caps it below 5.

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: submit the drafted scout profile for ProductClank's review, carrying the user's edits. That is clearly distinct from read-oriented siblings like get_scout_application, though it never explicitly distinguishes itself from the similarly named apply_as_scout.

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 a hard precondition: only call after the user has seen the draft and confirmed it is right. It also notes the call is free and that boundaries are required the first time, which shapes when the call is safe. It stops short of naming an alternative tool or a when-not-to-use case.

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.