Skip to main content
Glama

Get Site Profile

qualitykit.get_site_profile

Retrieve the approved Site Profile—brand, ICP, products, voice, pages, and keyword relevance—with confidence and freshness, or an ephemeral repo draft when Cloud is disconnected.

Instructions

Return the approved Site Profile (brand, ICP, products, voice, pages, keyword relevance), confidence, and freshness. Ephemeral repo draft when Cloud is not connected.

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": {
      "projectRoot": "<projectRoot>"
    },
    "name": "qualitykit.get_site_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiKeyNo
siteUrlNo
apiBaseUrlNo
projectRootYesAbsolute path to the website repository root

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the whole burden, and it does disclose one meaningful trait beyond the name: the ephemeral repo draft fallback when Cloud is not connected. It also signals that results carry confidence and freshness metadata. It omits permission/auth expectations implied by apiKey and whether a missing or unapproved profile yields an error, empty result, or draft.

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?

Two sentences, zero padding, and the payload contents are front-loaded ahead of the fallback caveat. Every clause carries information; nothing restates the title.

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?

With no output schema and no annotations, the description does the heavy lifting well: it enumerates the return payload and explains the degraded-mode source. The remaining gap is the configuration/auth semantics for three of four parameters, which the schema leaves undocumented and the description does not fill.

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

Parameters2/5

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

Schema coverage is only 25% — just projectRoot is documented as an absolute repository path. The description adds no meaning for apiKey, siteUrl, or apiBaseUrl, so an agent cannot tell when those are required versus optional or how they interact with the 'Cloud not connected' fallback, which is exactly the distinction that matters here.

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?

The description gives a specific verb-resource pair ('Return the approved Site Profile') and enumerates the returned contents — brand, ICP, products, voice, pages, keyword relevance, confidence, freshness. That is far more specific than a tautology. It does not, however, distinguish itself from siblings such as qualitykit.refresh_site_profile or qualitykit.update_site_profile, so an agent must infer the read-only vs. mutate split.

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 when-to-use statement and no exclusion naming an alternative. The closest thing to guidance is the fallback clause about returning an ephemeral repo draft when Cloud is not connected, which describes behavior rather than selection criteria. The agent is left to infer that this is the read path before audit/plan tools.

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