Skip to main content
Glama

sitekick_project_estimate

Read-onlyIdempotent

Review estimated generation credits for this exact current sealed project revision. Full-blueprint planning coverage includes all pages and assets, including potentially reused refinement pages. This is not a reservation ceiling or exact refinement charge. No generation starts. Retain the returned estimate_hash and pass it as reviewed_estimate_hash when explicitly starting generation.

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": {
      "payload": "<payload>",
      "site_ref": "<site_ref>"
    },
    "name": "sitekick_project_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYes
site_refYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive behavior, yet the description adds real value: it clarifies what the estimate spans (all pages and assets, including reused refinement pages), what it is not (a reservation ceiling or exact refinement charge), and that nothing is generated. The missing piece is whether the estimate can go stale or must be re-run before generation.

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?

Four short sentences, purpose front-loaded, with the exclusions (not a ceiling, not an exact charge, no generation) grouped before the required handoff instruction. Dense but every sentence carries distinct information; minor jargon load from "refinement" and "blueprint planning" wording.

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?

An output schema exists so return values need no prose, and the description still flags the one return field that matters downstream (estimate_hash). Combined with the two-phase workflow and scope caveats, only the input-side meaning of site_ref is left to the schema.

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% on two parameters, with a nested payload object, so the description must compensate. It adds meaningful semantics for revision_id by requiring the "exact current sealed project revision," but leaves project_id, site_ref, and the payload envelope unexplained beyond the raw patterns.

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 verb (review estimated generation credits) against a precisely scoped resource (this exact current sealed project revision). Scope qualifiers (current, sealed, full-blueprint coverage) separate it from a generic cost check, though it never names a sibling tool to contrast against.

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?

Makes the workflow position explicit: "No generation starts" and the returned estimate must be passed as reviewed_estimate_hash "when explicitly starting generation." That tells the agent this is a pre-flight step for a later generation call, but it does not state when to skip or re-run an estimate (e.g., after a revision changes).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources