Skip to main content
Glama
Sign In
Pharaoh - Your AI breaks things it can't see

Pharaoh - Your AI breaks things it can't see

by Pharaoh-so
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Setup

pharaoh_setup
Read-only

Check connection and setup status for the current repo before AI writes code; returns mapped-repo/access status, health link, and first-use guidance without writing files.

Instructions

Pharaoh's connection and setup status for the repo you're working in. Writes no files.

CALL THIS WHEN: • The user asks to set up Pharaoh, or to check its setup • Pharaoh was just connected and the user asks what to try first

RETURNS: Connection, mapped-repo and access status, a Codebase Health link, optional first-use choices, and the Pharaoh-first instructions line only when needed.

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": {
      "repo": "<repo>"
    },
    "name": "pharaoh_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoYesThe repo you're working in — one of your connected repos.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.3

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and writes are disallowed, and the description reinforces this with 'Writes no files.' More usefully, it discloses the response shape (connection, mapped-repo and access status, health link, optional first-use choices), which is needed because 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?

Front-loaded with the one-line purpose, then clean labeled sections for triggers and returns. Minor jargon ('the Pharaoh-first instructions line only when needed') is opaque, but no sentence is padding.

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?

A single-parameter read tool with no output schema, so the RETURNS section carries the needed weight and is present. Remaining gaps are minor, such as what happens with an unconnected repo.

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 100% for the single 'repo' parameter, which the schema already defines as 'one of your connected repos.' The description restates the repo scoping without adding syntax or enumeration guidance, so the baseline of 3 applies.

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 specific resource and what it reports: 'connection and setup status for the repo you're working in.' An agent can tell this apart from pharaoh_account or pharaoh_manage_repo by topic, though no sibling is named explicitly.

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?

The 'CALL THIS WHEN' block gives two concrete triggers (setup request, post-connection 'what next'). It has no explicit exclusions or pointers to sibling tools for adjacent needs, so it stops short of a full when/when-not spec.

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

Deploy Server

Other Tools