Skip to main content
Glama

Instructions for applying a scan's replacements to a codebase

get_agent_prompt
Read-onlyIdempotent

The step-by-step instructions for applying this scan's package: inspect the project, match each map entry to real files, change one reference at a time, validate, report what is unresolved. Never a blind search-and-replace. Still answered after the scan's files have been deleted. Reads only.

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": {
      "scan_id": "<scan_id>"
    },
    "name": "get_agent_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentNoDefault claude-code.
scan_idYesThe scan's id, from list_website_scans or the web app.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and closed-world, so the safety profile is settled. The description adds genuinely new behavioral facts: the response persists after the scan's files are deleted, and the payload is procedural guidance rather than executable action. It does not describe the response shape or whether the prompt varies meaningfully by agent.

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 core purpose is front-loaded and the clause list efficiently conveys the instruction content. The telegraphic, fragment-heavy style ("Reads only.", "Never a blind search-and-replace.") is dense but borders on choppy; a little connective tissue would read better without adding length.

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 two-parameter read-only retrieval with no output schema, the description covers what is returned, when it remains available, and the spirit of the instructions. The only meaningful gap is the effect of the agent parameter on the returned prompt, which the description never touches.

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 description coverage is 100%, so scan_id and the agent enum are already documented (including the claude-code default). The description adds only the framing that scan_id selects "this scan's package"; the agent parameter and its effect on the returned instructions are not mentioned at all.

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 concrete resource ("step-by-step instructions for applying this scan's package") and even enumerates the content of those instructions (inspect, match, change, validate, report). An agent knows it is retrieving guidance text for a scan, not data. It stops short of naming the sibling it complements (get_replacement_mapping), so it is clear but not fully differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Still answered after the scan's files have been deleted" gives a useful availability condition, and "Never a blind search-and-replace" hints at how the returned instructions should be used. But there is no explicit statement of when to call this versus get_replacement_mapping or get_website_report, so the routing decision is left to inference.

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