Skip to main content
Glama
GodPrompt MCP Server

GodPrompt MCP Server

Create a bounded GodPrompt task contract

create_work_contract
Read-onlyIdempotent

Create a SHA-256-fingerprinted task contract with explicit scope, acceptance criteria, verification commands, and prohibitions; missing details return NEEDS_DEFINITION, not inferred execution.

Instructions

Create a portable, SHA-256-fingerprinted task contract with explicitly provided scope, acceptance criteria, verification commands and prohibitions. Deterministic, read-only and stateless. Use classify_task first; missing details produce NEEDS_DEFINITION, never inferred commands or permission to execute.

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": "<task>"
    },
    "name": "create_work_contract"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYes
task_typeNoUNCLASSIFIED
risk_levelNomedium
allowed_pathsNo
success_criteriaNo
forbidden_actionsNo
verification_commandsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.1

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description's "Deterministic, read-only and stateless" largely echoes them. It does add genuinely new behavior: the SHA-256 fingerprint, that the tool never infers commands, and that a contract is not permission to execute — meaningful constraints an agent could not read from annotations alone.

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?

Three sentences, no filler, with the core output and its content front-loaded before the operational constraints. Nothing is redundant with the title or the schema.

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, so the description must convey the return value; naming the fingerprinted contract and the NEEDS_DEFINITION outcome does that adequately. Minor gaps remain around what the contract object actually contains and how large inputs are bounded.

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 0%, so the description must carry parameter meaning. It maps five of the seven parameters to intent (task, allowed_paths as "scope", success_criteria, forbidden_actions as "prohibitions", verification_commands), but never explains task_type values, risk_level semantics, or the array caps and length limits.

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?

The description gives a specific verb (Create) plus a precisely characterized resource: a portable, SHA-256-fingerprinted task contract carrying scope, acceptance criteria, verification commands and prohibitions. That is far more than a restatement of the name and lets an agent distinguish it from siblings like review_work_evidence or get_god_prompt without opening the schema.

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?

It states an explicit prerequisite ("Use classify_task first") and a decision rule for incomplete input (missing details produce NEEDS_DEFINITION). It stops short of naming situations where this tool should not be used at all, but the ordering guidance is clear and actionable.

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