Skip to main content
Glama

runway_getOrg

Retrieve organization details including credit balance and usage information to monitor account resources and track API consumption.

Instructions

Returns details like credit balance, usage details, and organization information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Inline handler function for the 'runway_getOrg' tool. Fetches organization details from Runway API using callRunway helper and returns the JSON stringified response.
    async () => {
      const org = await callRunway("/organization");
      return { content: [{ type: "text", text: JSON.stringify(org) }] };
    }
  • src/index.ts:210-218 (registration)
    Registration of the 'runway_getOrg' tool using server.tool, including name, description, empty input schema, and inline handler.
    server.tool(
      "runway_getOrg",
      "Returns details like credit balance, usage details, and organization information.",
      {},
      async () => {
        const org = await callRunway("/organization");
        return { content: [{ type: "text", text: JSON.stringify(org) }] };
      }
    );
  • Empty input schema (zod validation) for the 'runway_getOrg' tool, indicating no parameters required.
    {},
  • Helper function used by the tool handler to make authenticated API requests to the RunwayML backend.
    async function callRunway(
      path: string,
      opts: Partial<RequestInit> = {}
    ): Promise<unknown> {
      const res = await fetch(`${API_BASE}${path}`, {
        ...opts,
        headers: {
          Authorization: `Bearer ${SECRET}`,
          "X-Runway-Version": RUNWAY_VERSION,
          "Content-Type": "application/json",
          ...(opts.headers || {}),
        },
      } as RequestInit);
      if (!res.ok) throw new Error(`Runway ${res.status}: ${await res.text()}`);
      return res.json();
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states it 'Returns details,' implying a read-only operation, but doesn't cover other traits like error handling, rate limits, authentication needs, or response format. This is a significant gap for a tool with zero annotation coverage.

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 description is a single, efficient sentence that directly states the tool's purpose without waste. It's appropriately sized for a simple tool with no parameters, though it could be slightly more structured by front-loading key details more explicitly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (0 parameters, no output schema), the description is minimal. However, it lacks completeness for an informational tool: it doesn't specify what 'details' include beyond examples, doesn't mention error cases or data format, and with no annotations, it fails to provide sufficient context for reliable use.

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 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately doesn't mention any. Baseline for 0 parameters is 4, as it avoids unnecessary information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose with a specific verb ('Returns') and resource ('details like credit balance, usage details, and organization information'), making it easy to understand what it does. However, it doesn't explicitly differentiate from sibling tools like 'runway_getTask' which might also retrieve information, so it doesn't reach the highest score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention any context, prerequisites, or exclusions, such as when to choose this over 'runway_getTask' or other sibling tools, leaving the agent with minimal usage direction.

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/runwayml/runway-api-mcp-server'

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