Skip to main content
Glama

get_qurl

Fetch detailed information and access tokens for any qURL resource using its unique resource ID or qURL display ID.

Instructions

Get details of a qURL resource and its access tokens. Accepts either a resource ID (r_ prefix) or a qURL display ID (q_ prefix).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
resource_idYesThe resource ID (r_ prefix) or qURL display ID (q_ prefix) to fetch. If a q_ ID is passed, the API resolves it to the parent resource automatically.

Implementation Reference

  • The tool factory function `getQurlTool` defines the `get_qurl` MCP tool. Its handler calls `client.getQURL(input.resource_id)` to fetch a qURL resource and its access tokens, returning the data as JSON text.
    export function getQurlTool(client: IQURLClient) {
      return {
        name: "get_qurl",
        description:
          "Get details of a qURL resource and its access tokens. " +
          "Accepts either a resource ID (r_ prefix) or a qURL display ID (q_ prefix).",
        inputSchema: getQurlSchema,
        handler: async (input: z.infer<typeof getQurlSchema>) => {
          const result = await client.getQURL(input.resource_id);
          return {
            content: [
              {
                type: "text" as const,
                text: JSON.stringify(result.data),
              },
            ],
          };
        },
      };
    }
  • The input schema `getQurlSchema` uses Zod to validate a single `resource_id` parameter (accepts r_ or q_ prefixed IDs).
    export const getQurlSchema = z.object({
      resource_id: resourceIdSchema("fetch"),
    });
  • src/server.ts:7-7 (registration)
    The `getQurlTool` factory is imported from `src/tools/get-qurl.js`.
    import { getQurlTool } from "./tools/get-qurl.js";
  • src/server.ts:39-53 (registration)
    `getQurlTool` is added to the `toolFactories` array and registered with the MCP server via `server.tool()`.
    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);
  • The `resourceIdSchema` helper function produces the Zod schema used for the `resource_id` parameter.
    export function resourceIdSchema(verb: string) {
      return z
        .string()
        .min(1)
        .describe(
          `The resource ID (r_ prefix) or qURL display ID (q_ prefix) to ${verb}. ` +
            "If a q_ ID is passed, the API resolves it to the parent resource automatically.",
        );
    }
Behavior4/5

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

Discloses that it accepts two ID types and automatically resolves q_ IDs to the parent resource. Lacks permissions info, but no annotations to contradict.

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?

Two sentences, no waste, front-loaded with purpose. Perfectly concise.

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?

Covers input alternatives and resolution logic. Lacks description of output format, but tool is simple and no output schema exists.

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

Parameters5/5

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

Adds significant meaning beyond the schema: explains the different ID formats (r_ and q_ prefixes) and the automatic resolution behavior. Schema coverage is 100% but description enriches understanding.

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?

Clearly states 'Get details of a qURL resource and its access tokens', providing a specific verb and resource. Distinguishes from sibling tools like create, delete, list.

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?

Implies usage when you have a resource ID or qURL display ID, but does not explicitly state when to use this tool versus alternatives like list_qurls or resolve_qurl.

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