Skip to main content
Glama

Get an implementation prompt

get_ai_prompt
Read-only

Generates a paste-ready implementation prompt for Claude Code, Cursor, Lovable, or a generic AI agent in English or Korean, so you can hand component build instructions to your coding assistant.

Instructions

Return a paste-ready implementation prompt for Claude Code, Cursor, Lovable or a generic agent, in English or Korean. Pro components return a lock notice.

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": {
      "id": "<id>"
    },
    "name": "get_ai_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesComponent id.
targetNogeneric
languageNoen

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/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 safety is covered; the description still adds real behavioral value by disclosing that Pro components return a lock notice instead of a prompt. It does not describe the prompt's structure or length, but that is a minor omission for a read-only generator.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero filler, with the core capability front-loaded and the lock-notice caveat placed after it. Nothing could be removed without losing information.

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 three-parameter read-only tool with no output schema, the description covers what is produced, the target variation, the language variation, and the Pro lock behavior. Only id provenance and any failure mode when an invalid id is supplied are left unstated.

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 only 33% — just 'id' is documented — but the description compensates by naming every target option (Claude Code, Cursor, Lovable, generic) and both languages. The enum values and defaults are already self-evident in the schema, and nothing explains the id's expected format or source, so it lands at baseline-plus rather than strong.

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?

The description gives a specific verb and artifact ('Return a paste-ready implementation prompt') plus the supported targets and languages, so the tool's output is unmistakable. It stops short of explicitly contrasting itself with get_component or the other siblings, 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?

Usage is only implied: an agent can infer you call this when you want an implementation prompt rather than raw component data. There is no explicit when-to-use/when-not statement and no pointer to get_component or list_components for obtaining the id.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.