Skip to main content
Glama
Sign In

Ankra

by ai.ankra
OverviewDiscussionsAdmin

List AI endpoints

list_ai_endpoints
Read-only

The organisation's OpenAI-compatible AI endpoints (the twin of ankra ai endpoints list): each endpoint's id, name, provider, base_url, a masked key preview and when it was created and updated. Needs ai.manage (organisation owners and admins). Adding an endpoint, or changing its key or address, is a portal or ankra ai endpoints lane because it carries a provider key; rename_ai_endpoint and delete_ai_endpoint change the rest. Read-only. Never takes or returns a provider key.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_ai_endpoints"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Adds value beyond the readOnlyHint annotation: it states the required permission (ai.manage, owners and admins) and guarantees that no provider key is ever accepted or returned, with only a masked preview exposed. It does repeat 'Read-only' which the annotation already declares, and says nothing about volume or ordering of results, so it falls short of a 5.

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?

The returned-field list is front-loaded, and the routing/exclusion notes follow in logical order. The parenthetical 'the twin of `ankra ai endpoints list`' is CLI-specific filler an MCP agent does not strictly need, which keeps it below a 5.

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?

With no output schema, the description compensates by enumerating the fields returned, and it covers the auth requirement and the sibling split for mutations. An agent has everything needed to decide to call it and to interpret the response shape.

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 tool takes zero parameters, so there is no parameter meaning to add; the schema is trivially complete and the description correctly avoids inventing options. Baseline 4 applies for a no-parameter tool.

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?

Opens with a specific verb-plus-resource (list the organisation's OpenAI-compatible AI endpoints) and enumerates exactly what each record contains: id, name, provider, base_url, masked key preview, created/updated timestamps. It also names the siblings it is not (rename_ai_endpoint, delete_ai_endpoint), so an agent can distinguish it without opening another schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent away: adding an endpoint or changing its key/address must go through the portal or the `ankra ai endpoints` CLI lane, and rename_ai_endpoint/delete_ai_endpoint cover the remaining mutations. That is a clear when-to-use / when-not / alternative mapping rather than implied 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