Skip to main content
Glama
Sign In

Ankra

by ai.ankra
OverviewDiscussionsAdmin

Diff stack profile versions

diff_stack_profile_versions
Read-only

Compare two published versions of a stack profile (the twin of ankra stack-profiles diff): the add-ons, manifests and parameters one adds, removes or changes against the other. Read-only.

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": {
      "from_version": "<from_version>",
      "to_version": "<to_version>"
    },
    "name": "diff_stack_profile_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
profile_idNoThe stack profile id (UUID) from list_stack_profiles. Give this or profile_name.
to_versionYesThe newer version.
from_versionYesThe older version.
profile_nameNoThe stack profile's exact name, instead of profile_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces that while adding genuinely new context: the diff is restricted to published versions and covers three specific artifact categories. It does not explain output shape or what happens for identical versions, but for a read-only tool with annotations covering safety, this is solid added value.

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?

A single front-loaded sentence plus a short read-only tag; every clause carries information. The CLI-twin parenthetical is only mildly redundant for agents without CLI familiarity, and 'Read-only' partially duplicates the annotation.

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?

No output schema exists, and the description compensates by naming the three categories the diff reports. With four fully documented parameters and a readOnly annotation, an agent has everything needed to select and invoke it correctly.

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 100%, so profile_id vs profile_name and the from/to version integers are already fully documented, including the older/newer relationship. The description adds no parameter-level meaning beyond that, so baseline 3 applies.

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 specific verb (compare/diff) and resource (two published versions of a stack profile), and enumerates exactly what is compared: add-ons, manifests and parameters added, removed or changed. This is clearly distinguishable from siblings such as get_stack_profile, list_stack_profile_deployments, or save_stack_profile_version.

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?

The description implies usage by scoping it to 'two published versions' and noting it mirrors a CLI command, but it never states when to pick this over get_stack_profile, get_stack_profile_draft, or export_stack_profile_iac. No exclusions or prerequisites (e.g. that drafts cannot be diffed) are spelled out explicitly.

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

All Ankra 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