Skip to main content
Glama

Get stack profile summary

get_stack_profile_summary
Read-only

Read the approved summary of one stack profile version (the twin of ankra stack-profiles summary get): what the version deploys, as statements built from its own resources, its coverage gaps and its parameters. With fact_id it returns the evidence behind one statement instead. Needs profiles.read and a profile visible in this project. Read-only: generating, reviewing, approving and withdrawing a summary are not offered here.

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": {
      "profile_id": "<profile_id>",
      "version": "<version>"
    },
    "name": "get_stack_profile_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
fact_idNoOne fact of a claim, for its evidence.
versionYesThe published version number.
profile_idYesThe stack profile's id (UUID), from list_stack_profiles.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description adds the authorization prerequisite (profiles.read), the visibility scoping rule (profile must be in this project), and an explicit statement of which mutation-adjacent summary operations are absent, which is consistent with the read-only hint. It stops short of describing response shape or any limits, but for a read tool that is a minor gap.

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 purpose in the first clause and no filler sentences; each subsequent clause adds a distinct fact (contents, fact_id branch, prerequisites, scope). The parenthetical CLI twin reference ('ankra stack-profiles summary get') is mildly extraneous for an agent but does not impede selection.

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?

For a three-parameter read-only tool with no output schema, the description supplies what the call returns (statements, coverage gaps, parameters, or one fact's evidence), the access requirement, and the operation boundary. Only minor details such as response formatting or size expectations are absent, which is acceptable at this complexity.

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

Parameters4/5

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

The schema already documents all three parameters at 100% coverage, so the baseline is 3. The description adds genuine meaning: it clarifies that version means the published/approved version and that fact_id switches the tool from returning the whole summary to returning the evidence behind one statement — a behavioral distinction the schema's one-line fact_id description only hints at.

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

Purpose5/5

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

States a precise verb and resource: read the approved summary of one stack profile version, enumerating its contents (deployment statements, coverage gaps, parameters) and the fact_id variant that returns evidence for a single statement. The word 'approved' plus the explicit 'not offered here' list separates it from the draft-oriented siblings like get_stack_profile_draft.

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

Usage Guidelines5/5

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

Gives the positive condition (an approved/published version, with profiles.read and the profile visible in the project) and an explicit exclusion set — generating, reviewing, approving and withdrawing summaries are not offered here — plus a concrete branch for when fact_id is supplied. An agent knows both when to call it and when to look elsewhere.

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.