Skip to main content
Glama
GodPrompt MCP Server

GodPrompt MCP Server

Get phase-specific GodPrompt guidance

get_tailored_guidance
Read-onlyIdempotent

Fetch the task-type protocol or quality gate for one phase in small chunks to avoid loading the full reference. Returns targeted guidance without executing or verifying tasks.

Instructions

Return only the relevant task-type protocol or quality gate for one phase, paged into small bounded chunks. More efficient than loading the entire reference; no tool execution or verification.

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": {
      "task_type": "<task_type>"
    },
    "name": "get_tailored_guidance"
  }
}

Input Schema

NameRequiredDescriptionDefault
phaseNoexecute
startNo
max_charsNo
task_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.4.2

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered structurally. The description adds genuine context beyond them: 'no tool execution or verification' and that output is chunked. It stops short of the behavior an agent most needs - how truncation is signalled and whether more content remains - which is a real gap given there is no output schema.

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?

A single dense sentence with the resource and the chunking constraint front-loaded and no filler. It is efficient, though the comma-tacked clauses make the paging behavior slightly harder to parse than a short second sentence would.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description should explain how to continue pagination (advance start, watch max_chars) and how to detect the end of content; it does not. The purpose and no-execution caveat are covered, and schema defaults make continuation guessable, so it is adequate but incomplete for a paged retrieval tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 full burden across four parameters. It conceptually gestures at phase ('for one phase'), task_type ('task-type protocol'), and paging ('small bounded chunks'), but never names or bounds start/max_chars, never explains the enum values, and never clarifies the phase vs task_type relationship.

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 resource ('Return the relevant task-type protocol or quality gate for one phase') and states the scope restriction ('only the relevant', 'for one phase'). That distinguishes it from the broader sibling get_god_prompt and from get_protocols/get_gates, though the 'protocol or quality gate' duality leaves slight ambiguity about which artifact a given call returns.

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?

'More efficient than loading the entire reference' implies the alternative (the full-reference tool) and the condition that selects this one, so usage is inferable rather than explicit. There is no stated when-not, no guidance on which phase/task_type combination to request, and no mention of when the full reference is actually needed.

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