Skip to main content
Glama
Sign In

pageaudit

by online.pageaudit
OverviewDiscussionsAdmin

Get fix prompt

get_fix_prompt
Read-onlyIdempotent

Read a saved prompt. It costs nothing, even after plan expiry. Preserve the complete prompt and license. Use it only for license.domain. This does not authorize deployments or infrastructure changes. Uses the authenticated owner and active organization. Returns the immutable text. A missing or foreign prompt returns 404. Does not consume allowance, credit or require an active plan.

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_fix_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesSaved prompt ID from generation or the private list.
guest_tokenNoPrivate owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / guest_token / description
      Added value: +"Private owner token returned by guest creation. Sent in X-Guest-Token; reuse it for this owner's resources."
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Goes well past the annotations: cost is zero even after plan expiry, no allowance/credit is consumed, no active plan is required, ownership is scoped to the authenticated owner and active organization, and a missing or foreign prompt returns 404. The readOnlyHint/idempotentHint annotations already cover the safety profile, so this added billing, auth, and error behavior is genuine incremental value. Minor gap: the exact response payload shape is only hinted at as 'the immutable text'.

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 core action and cost model, and most sentences carry distinct information. The cost point is stated twice ('costs nothing, even after plan expiry' and 'does not consume allowance, credit or require an active plan'), which is the only real redundancy; the sentence fragments are choppy but scannable.

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

Completeness5/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 tool with full schema coverage, rich annotations, and no output schema, nothing an agent needs is missing: cost, plan requirement, auth/ownership scoping, error behavior, and immutability are all covered.

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%, so both 'id' and 'guest_token' are already documented in the schema, which sets the baseline at 3. The description adds adjacent context (owner- and organization-scoped resolution, 404 for a foreign prompt) without explaining either parameter directly, so no uplift is warranted.

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?

Opens with a specific verb and resource ('Read a saved prompt') and adds that it returns the immutable text, which distinguishes it from the generate_* and list_*_fix_prompts siblings even though none is named explicitly. The single-ID retrieval model is clear from the description plus the required 'id'.

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?

It supplies usage constraints ('Use it only for license.domain', 'does not authorize deployments or infrastructure changes') but never says when to pick this over list_domain_fix_prompts or generate_fix_prompt. The routing signal is implied by 'saved prompt' + ID rather than stated.

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

All pageaudit toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources