Skip to main content
Glama
okareo-ai

Okareo MCP Server

Official
by okareo-ai
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

List Tenants

list_tenants
Read-onlyIdempotent

List every Okareo organization available in this session, with the active one marked. OAuth required; Bearer-key sessions see a notice.

Instructions

List every Okareo organization you have access to in this MCP session.

    The currently-active organization is marked ``is_current: true``. The
    active organization is determined at sign-in (the token this session
    presents is already scoped to it). Only available on OAuth-authenticated
    sessions; on Bearer-API-key sessions returns
    ``tenant_selection_requires_oauth``.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/destructive hints, and the description adds meaningful context: the is_current marker and the OAuth-only constraint, going beyond 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?

Three sentences, each providing distinct value: scope, active marker, and authentication requirement. No fluff, well organized.

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 output schema exists and the tool has no parameters, the description fully covers behavior, including edge cases like non-OAuth sessions.

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 has zero parameters, so the description need not explain semantics. The description implicitly confirms no inputs are needed.

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 ('List') and resource ('every Okareo organization you have access to'), and distinguishes itself from siblings like switch_tenant by focusing on listing rather than switching.

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 states when the tool is available (OAuth-authenticated sessions) and what happens on Bearer-API-key sessions, giving clear usage context and an alternative behavior.

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/okareo-ai/okareo-mcp'

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