Skip to main content
Glama

resolve_qurl

Resolve a qURL access token to retrieve the target URL and temporarily open firewall access for your IP.

Instructions

Resolve a qURL access token to get the target URL and open firewall access. After resolution, the target URL is accessible from your IP for the duration specified in access_grant.expires_in seconds.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
access_tokenYesThe access token from a qURL link (e.g., at_k8xqp9h2sj9lx7r4a)

Implementation Reference

  • The factory function that creates the resolve_qurl tool, including its handler that calls client.resolveQURL() and formats the response.
    export function resolveQurlTool(client: IQURLClient) {
      return {
        name: "resolve_qurl",
        description:
          "Resolve a qURL access token to get the target URL and open firewall access. " +
          "After resolution, the target URL is accessible from your IP for the duration " +
          "specified in access_grant.expires_in seconds.",
        inputSchema: resolveQurlSchema,
        handler: async (input: z.infer<typeof resolveQurlSchema>) => {
          const result = await client.resolveQURL(input);
          return {
            content: [
              {
                type: "text" as const,
                text: JSON.stringify(result.data),
              },
            ],
          };
        },
      };
    }
  • Zod schema for the resolve_qurl tool input, requiring a non-empty 'access_token' string.
    export const resolveQurlSchema = z.object({
      access_token: z
        .string()
        .min(1)
        .describe("The access token from a qURL link (e.g., at_k8xqp9h2sj9lx7r4a)"),
    });
  • TypeScript interface for ResolveOutput returned by the API call.
    export interface ResolveOutput {
      target_url: string;
      resource_id: string;
      access_grant: {
        expires_in: number;
        granted_at: string;
        src_ip: string;
      };
    }
  • TypeScript interface for ResolveInput (client-side type definition).
    export interface ResolveInput {
      access_token: string;
    }
  • src/server.ts:39-54 (registration)
    Tool registration: resolveQurlTool is included in the toolFactories array and registered via server.tool() in the loop.
    const toolFactories = [
      createQurlTool,
      resolveQurlTool,
      listQurlsTool,
      getQurlTool,
      deleteQurlTool,
      extendQurlTool,
      updateQurlTool,
      mintLinkTool,
      batchCreateTool,
    ] satisfies ToolFactory[];
    
    for (const factory of toolFactories) {
      const tool = factory(client);
      server.tool(tool.name, tool.description, tool.inputSchema.shape, tool.handler);
    }
Behavior4/5

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

With no annotations provided, the description discloses the side effect of opening firewall access and the time-bound nature of the access (expires_in seconds). This goes beyond basic schema information, though it could be more explicit about what the target URL is used for.

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?

The description is just two sentences, front-loading the purpose and adding a key behavioral detail in the second sentence. No unnecessary words.

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

Completeness4/5

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

For a simple tool with one parameter and no output schema, the description covers the purpose, the effect (firewall opening), and the duration. It could mention what is returned (target URL) but is largely complete.

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?

The input schema has 100% description coverage for the single parameter. The tool description does not add additional semantics beyond what is already in the schema parameter description.

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 uses a specific verb 'resolve' on a resource 'qURL access token', clearly stating the outcome: 'get the target URL and open firewall access'. This distinguishes it from sibling tools such as create, delete, or update.

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

Usage Guidelines3/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. The usage context is implied by the tool name and description, but no alternative tools are mentioned or exclusions given.

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/layervai/qurl-mcp'

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