Skip to main content
Glama
Sign In

Ankra

by ai.ankra
OverviewDiscussionsAdmin

Unshare stack profile

unshare_stack_profile

Stop sharing a stack profile with an organisation (the twin of ankra stack-profiles unshare). Stacks it already deployed keep running.

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": {
      "share_id": "<share_id>"
    },
    "name": "unshare_stack_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
share_idYesThe share id, from list_stack_profile_shares.
profile_idNoThe stack profile id (UUID) from list_stack_profiles. Give this or profile_name.
profile_nameNoThe stack profile's exact name, instead of profile_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations mark this as a non-read-only, non-idempotent, non-destructive mutation, and the description adds genuinely useful context beyond that: already-deployed stacks keep running, so unsharing does not tear down workloads. It still does not disclose permission/ownership requirements or whether the share can be re-created afterwards.

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?

Two short sentences with the core action front-loaded and the most decision-relevant caveat (deployed stacks keep running) placed immediately after. The parenthetical CLI reference is marginally useful and slightly expendable, but costs little.

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 mutation with no output schema and safety already covered by annotations, the description supplies what an agent actually needs: the action, its scope, and the fact that deployed stacks are unaffected. Only secondary details such as re-share reversibility or authorisation requirements are missing.

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%, with `share_id`, `profile_id`, and `profile_name` all documented in the schema itself, including where to obtain each value. The description adds no parameter-level meaning, so the baseline of 3 applies — the schema does all the work.

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 states a specific verb and resource ("Stop sharing a stack profile with an organisation"), which is unambiguous about the operation being performed. It does not name the sibling tool `share_stack_profile` as its inverse, instead referencing the CLI command `ankra stack-profiles unshare`, so sibling differentiation via the tool catalog is left implicit.

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?

Usage is only implied: an agent must infer that this is the inverse of sharing and that it applies when a profile should no longer be visible to an organisation. There is no explicit when-to-use, when-not-to-use, or named alternative in the tool catalog, though the operation is narrow enough that the intent is rarely ambiguous.

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