Skip to main content
Glama
AlephantAI

Alephant MCP

Official
by AlephantAI

get_my_scope

Read-onlyIdempotent

Retrieve the current virtual key scope, usage limits, and accessible resources for your AI API key.

Instructions

Returns the current virtual key scope, limits, and accessible resources.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler that registers and implements the 'get_my_scope' tool. It calls `cockpit.scope()` via `safeCall` and returns the result.
    export function registerVkScopeTools(server: McpServer, deps: ToolDeps): void {
      server.tool("get_my_scope", {}, async () => {
        const cockpit = requireCockpit(deps);
        return safeCall(() => cockpit.scope(), "vk");
      });
    }
  • The `ScopeResponse` type definition – the schema for what `get_my_scope` returns (workspaceId, workspaceName, keyId, keyLabel, optional departmentId/agentId).
    export interface ScopeResponse {
      workspaceId: string;
      workspaceName: string;
      keyId: string;
      keyLabel: string;
      departmentId?: string;
      agentId?: string;
    }
  • The `CockpitClient.scope()` method that makes the actual HTTP GET request to `/api/v1/cockpit/scope`.
    async scope(): Promise<ScopeResponse> {
      const { data } = await this.http.get("/api/v1/cockpit/scope");
      return data as ScopeResponse;
    }
  • Registration wiring: in 'vk' mode, `registerVkScopeTools` is called which registers `get_my_scope`.
    if (mode === "vk") {
      registerVkScopeTools(server, deps);
      registerVkBudgetTools(server, deps);
      return;
    }
  • The tool description for 'get_my_scope' in the TOOL_DESCRIPTIONS map in the registry.
    get_my_scope:
      "Returns the current virtual key scope, limits, and accessible resources.",
Behavior4/5

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

Annotations already provide readOnlyHint and idempotentHint. The description adds value by specifying exactly what is returned (scope, limits, accessible resources), reinforcing the safe read behavior without contradicting annotations.

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 description is a single sentence of 10 words, efficiently stating the purpose. It is front-loaded with the verb 'Returns' and contains no extraneous information.

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?

Given the tool has no parameters, annotations indicate safety, and no output schema exists, the description sufficiently explains what the tool does. An agent can correctly infer that calling this tool is safe and returns scope information.

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 input schema has zero parameters with 100% coverage. The description does not need to add parameter information. Baseline of 4 is appropriate as no parameter details are required.

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 uses the verb 'Returns' and specifies the resource as 'current virtual key scope, limits, and accessible resources'. It clearly distinguishes from siblings like get_my_budget or get_usage_summary by focusing on scope and limits.

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 does not provide explicit guidance on when to use this tool versus alternatives. Usage is implied as a simple read of scope information, but no exclusions or contexts are given.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AlephantAI/alephant-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server