Skip to main content
Glama

Get Organization Details

get_org_details
Read-only

Retrieve an organization's plan, execution quota, reset date, seats, project usage, and test health to answer plan, quota, and usage questions.

Instructions

Answer plan and quota questions for one organization: "what plan are we on", "how many executions are left", "what happens when we run out", "can we buy more". Returns the plan, executions limit/used/remaining and the reset date, seats and projects used against the plan (limit null = unlimited), extra executions (top-ups) on offer and active, the projects this token can see with the executions each used, and org test health (pass/fail/flaky per project over window days). quota.message is TestDino's own answer for what the quota state means and what to do next — relay it to the user as written. Any section can be {status:"unavailable"}: that read failed, so say it could not be checked; it never means zero or none. Takes the orgId from health. A token covering only some projects of the org sees only those projects and no org-wide totals. Read-only: buying executions or changing the plan happens on the billing page, never through this tool.

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": {
      "orgId": "<orgId>"
    },
    "name": "get_org_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgIdYesOrganization ID (org_<id>), as health returns it
windowNoDays to cover (default 30)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare a safe read, but the description adds substantial behavior: any section can return {status:"unavailable"} and must be reported as unchecked rather than zero, limit null means unlimited, partial-token visibility hides org-wide totals, and quota.message must be relayed verbatim. These are non-obvious traits an agent could not infer from the schema or annotations.

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?

It is a single dense block, but it is front-loaded with the purpose and the answerable questions before the payload inventory and caveats. Nearly every sentence carries operational weight, though the payload enumeration could be tightened slightly for readability.

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?

There is no output schema, so the description carries the full burden of describing return values, and it does so section by section, including the unavailable-status convention and the unlimited-limit sentinel. Nothing an agent needs to call and interpret this tool correctly appears to be 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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: `window` is clarified as the number of days over which per-project test health is reported, and orgId is tied to the value health returns. Only the enum semantics of window remain purely schema-derived.

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 opening sentence names a specific verb and resource (answer plan and quota questions for one organization) and enumerates the concrete questions it resolves, then lists the exact payload sections. It is clearly distinguishable from siblings like health or get_project_details because org-level plan/quota scope is stated explicitly.

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?

Usage is grounded in example questions the tool answers and a routing hint ('Takes the orgId from health'), plus a clear exclusion that billing/plan changes happen on the billing page, never through this tool. It stops short of naming a sibling to use for project-scoped questions, so the alternative routing is only implied.

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