Skip to main content
Glama

Strengthen a bug-bounty submission

assist_submission
Read-only

Submission & escalation co-pilot for a bug-bounty finding. Paste your DRAFT finding (and what you already tried / couldn't achieve) and get a grounded brief built from the closest REAL disclosed reports: (1) precedent & validity — is this an accepted class, with citable reports (ammunition if it was disputed/closed); (2) what's novel/stronger about yours — what to lead with; (3) an escalation playbook INCLUDING moves you may NOT have tried, each with honest feasibility; (4) submission-framing tips.

Every cited report URL is validated against the retrieved corpus — ungrounded citations are flagged in 'citations.ungrounded' with 'citations_grounded=false', so the brief can't smuggle in a fabricated precedent (this guards the citations only — never read it as a verdict on whether your finding itself is real). Optional 'query' overrides the retrieval text (default: the finding itself); limit (default 15) caps the prior-art reports. Complements find_attack_approaches (which returns the raw prior-art cards).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "finding": "<finding>"
    },
    "name": "assist_submission"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
findingYes

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 already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: citations are validated against the retrieved corpus, ungrounded ones surface in 'citations.ungrounded' with 'citations_grounded=false', and it explicitly scopes that guard to citations only, not validity of the finding. No contradiction with annotations.

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 purpose and the numbered deliverable list, then tucks caveats and parameter notes at the end where they belong. It is dense but every clause carries information; the only mild cost is the long parenthetical caveat about citation grounding.

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?

There is no output schema, yet the description sketches the brief's sections and names the citation fields an agent should inspect, which is the right level of detail for a read-only analysis tool. It could say more about the returned report's shape or whether results are paginated, but nothing essential to invoking it 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?

Schema description coverage is 0%, so the description carries the burden, and it does: 'query' is explained as an override of the retrieval text defaulting to the finding itself, and 'limit' (default 15) caps how many prior-art reports are pulled. The required 'finding' param is described via the paste-your-draft instruction, though not as explicitly as the optional two.

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 resource ('Submission & escalation co-pilot for a bug-bounty finding') and enumerates the four deliverables (precedent, novelty, escalation playbook, framing tips). It explicitly distinguishes itself from the sibling find_attack_approaches, which returns raw prior-art cards.

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?

Clearly says what to feed it ('paste your DRAFT finding and what you already tried') and routes the agent to find_attack_approaches when raw prior-art cards are wanted. It stops short of stating when NOT to use it, e.g. before a finding exists, so it is not a full 5.

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.