Skip to main content
Glama
Sign In

Ankra

by ai.ankra
OverviewDiscussionsAdmin

Share stack profile

share_stack_profile

Share a stack profile your organisation owns with another organisation, which can then list and deploy it (the twin of ankra stack-profiles share).

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": {
      "organisation_slug": "<organisation_slug>"
    },
    "name": "share_stack_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
organisation_slugYesThe slug of the organisation to share with.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the safety bar is lower. The description adds genuine context beyond them — this is an access grant that lets the other organisation list and deploy the profile — but it says nothing about revoking that grant, what happens on a repeated share (non-idempotent), or required permissions.

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 stating actor, action, and effect, with no filler. The parenthetical CLI-equivalence clause is mildly extraneous for an agent that has no shell access.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only three fully documented parameters and annotations covering the safety profile, the description covers enough to invoke the tool correctly. It remains thin on outcomes — what is returned, how to verify an existing share, and whether re-sharing duplicates or errors — which matter for a non-idempotent cross-organisation grant.

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% and each of the three parameters is documented in the schema, so the baseline of 3 applies. The description's 'your organisation owns' and 'share with' framing only loosely reinforces the ownership/recipient semantics already stated in the schema and adds no format or edge-case detail.

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 names a specific verb and resource ('Share a stack profile') and adds scope: the caller must own the profile and the recipient gains the ability to list and deploy it. That effect clause distinguishes it from generic profile mutations, though it never names the obvious counterpart tools (unshare_stack_profile, list_stack_profile_shares) that an agent might confuse it with.

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?

It implies the usage context (your organisation owns the profile, sharing is with another organisation) but gives no explicit when-to-use/when-not guidance, no prerequisites such as ownership or permission checks, and no alternative tools to consult. The 'twin of `ankra stack-profiles share`' note is a CLI cross-reference rather than selection guidance.

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