Skip to main content
Glama

sitekick_project_get

Read-onlyIdempotent

Read the exact project revision and blueprint.

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

Input Schema

NameRequiredDescriptionDefault
payloadYes
site_refYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds almost nothing beyond that — the word "exact" weakly suggests a pinned, deterministic revision read, but there is no mention of required permissions, freshness/staleness semantics, or failure modes for an open-world read.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no filler, which is structurally clean, but the brevity crosses into under-specification rather than economy — no wasted words, yet not enough words to do the job.

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

Completeness2/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-value explanation is not required, and annotations cover the safety profile. However, the tool has a nested payload object, a regex-constrained site reference, and sits inside a dense cluster of project/blueprint siblings — for that complexity, one sentence leaves key context (what "blueprint" means here, how site_ref and project_id combine) unexplained.

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

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across two required inputs (site_ref and the nested payload.project_id), and the description mentions neither parameter nor the site/project scoping relationship. Because the schema documents only shapes and regex patterns, the description was the only place to explain what these identifiers mean and it does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

It has a concrete verb ("Read") and a resource ("project revision and blueprint"), but "exact project revision and blueprint" is ambiguous about what is actually returned and does not differentiate it from siblings like sitekick_project_estimate, sitekick_project_update, or sitekick_release_get. An agent gets the gist (a read of project state) but not a clear picture of the operation's scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this over the other project/release/blueprint tools, no prerequisites (e.g., does a project need to be sealed or prepared first?), and no exclusions. The single sentence leaves selection entirely to inference from the name.

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