Skip to main content
Glama
Sign In

Ankra

by ai.ankra
OverviewDiscussionsAdmin

Set personal AI keys allowed

set_personal_ai_keys_allowed

Set whether AI work a member of this organisation starts may run on that member's personal AI keys (allowed true, the default) or stays on the organisation's own AI setup (false). Members keep their keys either way, and an organisation that runs AI on its own endpoint never uses them. get_ai_settings reads the current value as personal_ai_keys_allowed. Needs the ai.manage permission (organisation owners and admins), and only the person themselves may call it: refused for a service account, an AI agent, a subworker and a dispatched or autonomous run.

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": {
      "allowed": "<allowed>"
    },
    "name": "set_personal_ai_keys_allowed"
  }
}

Input Schema

NameRequiredDescriptionDefault
allowedYestrue lets members' personal keys serve the work they start here; false keeps the organisation's work off them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, it describes what the setting controls, the default behavior, that members retain their keys, and that an organisation running on its own endpoint never uses them. It also discloses authorization requirements and exact caller exclusions, which are critical behavioral details.

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?

The setting and its true/false meaning are front-loaded, followed by permission and caller constraints. Despite the authorisation detail, every sentence adds useful context and there is no filler.

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?

For a one-parameter mutation with no output schema, the description covers the setting semantics, default, permissions, caller restrictions, and the read counterpart. An agent has enough information to invoke it correctly and anticipate authorization failures.

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 the single boolean parameter at 100% coverage. The description adds useful meaning: true is the default and lets personal keys serve work started here, while false keeps organisation work off those keys.

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?

The description states a specific verb and setting: whether members' AI work may run on their personal keys. It explains both boolean outcomes and contrasts the tool with get_ai_settings, which reads the same value.

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

Usage Guidelines4/5

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

It gives clear applicability context: the default is true, get_ai_settings is the read counterpart, ai.manage is required, and callers are restricted to the person themselves. It does not explicitly say when to choose another tool, but the read/write split is clear.

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