Skip to main content
Glama

create_geomi_api_resource_application

Create API resource applications for Aptos blockchain interactions within Geomi organizations to generate API keys for development workflows.

Instructions

Create a new Application for your Geomi Organization. Geomi is the essential toolkit for Aptos developers. This tool can be used to create an API resource application to then create api keys for general Aptos blockchain interactions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
descriptionNoThe description of the application.
nameYesThe name of the application. Must be between 3 and 32 characters long, with only lowercase letters, numbers, dashes and underscores.
networkYesThe network to create the application for. Can be devnet, testnet or mainnet.
organization_idYesThe organization id to create the application for.
project_idYesThe project id to create the application for.

Implementation Reference

  • The handler implementation for the "create_geomi_api_resource_application" tool.
    export const createApiResourceApplicationTool = {
      description:
        "Create a new Application for your Geomi Organization. Geomi is the essential toolkit for Aptos developers. This tool can be used to create an API resource application to then create api keys for general Aptos blockchain interactions.",
      execute: async (
        args: {
          description?: string;
          name: string;
          network: string;
          organization_id: string;
          project_id: string;
        },
        context: any
      ) => {
        try {
          await recordTelemetry(
            { action: "create_api_resource_application" },
            context
          );
          const geomi = new Geomi(context);
          const application = await geomi.createApplication({
            args: {
              description: args.description ?? null,
              name: args.name,
              network: args.network,
              service_type: "Api",
            },
            organization_id: args.organization_id,
            project_id: args.project_id,
          });
          return JSON.stringify(application);
        } catch (error) {
          return `❌ Failed to create application: ${error}`;
        }
      },
      name: "create_geomi_api_resource_application",
      parameters: CreateApiResourceApplicationToolScheme,
    };
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Create a new Application' implying a mutation, but doesn't disclose behavioral traits such as required permissions, whether the operation is idempotent, rate limits, or what happens on failure. The mention of creating API keys is contextual but not detailed enough for transparency.

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 appropriately sized with two sentences. The first sentence directly states the purpose, and the second adds useful context about Geomi and API keys. It's front-loaded and avoids unnecessary verbosity, though the second sentence could be more tightly integrated.

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 no annotations and no output schema, the description is incomplete for a mutation tool. It lacks details on behavioral aspects like error handling, response format, or side effects. The context about Geomi and API keys is helpful but doesn't compensate for missing operational transparency.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all 5 parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema, such as explaining relationships between parameters or usage examples. Baseline 3 is appropriate when schema does the heavy lifting.

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 action ('Create a new Application') and the resource ('for your Geomi Organization'), with additional context about Geomi's purpose. It distinguishes from siblings like 'create_gas_station_application' by specifying 'API resource application' and mentions creating API keys for Aptos blockchain interactions, though not all sibling differences are explicit.

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?

No explicit guidance on when to use this tool versus alternatives like 'create_gas_station_application' or 'create_geomi_project'. The description mentions creating API keys as a follow-up, but lacks clear prerequisites, exclusions, or comparative context with other Geomi tools.

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/aptos-labs/aptos-npm-mcp'

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