Skip to main content
Glama

Get organisation

get_organisation
Read-only

The organisation this token or session is bound to (the twin of ankra org current): id, name, slug, when it was created, member and service-principal counts, and its organisation-wide settings (automatic agent upgrades, MFA requirement, proactive AI insights, security baseline). Use this first when a request says 'my organisation' or 'our account' and nothing else names it. Read-only.

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": "get_organisation"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

readOnlyHint=true already declares the safety profile, and 'Read-only' merely restates it. The genuine added value is the disclosure of payload contents — the field list and the specific org-wide settings surfaced (auto agent upgrades, MFA, AI insights, security baseline) — which no annotation or output schema provides. It stops short of covering staleness or caching behaviour.

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?

Front-loaded with the identity of the resource, then the returned fields, then the usage trigger — a sensible order. The trailing 'Read-only' duplicates the readOnlyHint annotation and is the one phrase that does not earn its place.

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 carries the burden of telling the agent what comes back, and it does so concretely, including the org-level settings an agent might otherwise fetch separately. Combined with the CLI parity note and the usage trigger, nothing needed to call it correctly is missing.

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 the baseline is 4; there is no input for the description to explain and it correctly does not invent any. Nothing about scoping is left implicit beyond the token/session binding, which the description does mention.

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?

States a specific verb+resource ('get the organisation this token or session is bound to') and enumerates exactly what is returned: id, name, slug, creation time, member and service-principal counts, and organisation-wide settings. It also explicitly differentiates from neighbouring org tools by saying it is the twin of `ankra org current`, and it is clearly not the member/role/variable listers.

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?

Gives an explicit trigger: use it first when a request says 'my organisation' or 'our account' and nothing else names it. That resolves the common ambiguity with `get_current_project` or a cluster-scoped call. It does not state when NOT to use it (e.g. when an org id is already supplied), so it falls short of a full when/when-not pair.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.